Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:

Assigned Teams:

Sharding EMEA
Backwards Compatibility:
Fully Compatible
Sprint:
Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13
Linked BF Score:
20
Story Points:
1
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The numInitialChunks parameter can be used to spread chunks across shards when sharding an empty collection with hashed shard key. Considering that the auto splitter gone away and that the number of chunks does not matter anymore, this option has no real value anymore.

causes

SERVER-83005 Reintroduce numInitialChunks parameter (IDL only) to maintain backward compatibility

Closed

is depended on by

SERVER-82611 Remove the 'numInitialChunks' parameter from the initial split policies for shardCollection

Closed

is related to

SERVER-81884 Get rid of featureFlagOneChunkPerShardEmptyCollectionWithHashedShardKey once v8.0 branches out

Closed

related to

SERVER-83006 Remove deprecated numInitialChunk parameter

Backlog

SERVER-76405 Reduce the initial minimum number of chunks to 1 per shard for empty collections with hashed shard key

Closed

Assignee:: Robert Sander
Reporter:: Pierlauro Sciarelli
Participants:: Antonio Fuschetto, Githook User, Pau Baldillou Salse, Pierlauro Sciarelli, Robert Sander
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: Mar 10 2023 03:15:22 PM UTC
Updated:: Jan 19 2024 08:11:27 AM UTC
Resolved:: Nov 07 2023 10:27:58 AM UTC
Confidence Status Last Update:: 25/Sep/23 8:17 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates