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:
- sharding-wfbf-day

Assigned Teams:

Sharding EMEA
Backwards Compatibility:
Fully Compatible
Sprint:
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
Confidence Status:
None
Work Order:
3

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

Following the removal of the auto-splitter in versions >= v6.0.3, balancing does not happen anymore on number of chunks but on actual data size and the balancer is issuing moveRange commands (DOCS-15363) to atomically split+move subparts of a chunk.

Purpose of this ticket is to change the default behavior for creating/distributing chunks when sharding an empty collection with hashed shard key: one chunk per shard, in line with the decision taken also for resharding (SERVER-68050).

is related to

SERVER-82068 Investigate handling of MinKey and MaxKey in moveChunkParallel helper

Open

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

Closed

SERVER-82216 Make a more even distribution of chunks through shards for initial split policies with zones

Backlog

SERVER-74747 Deprecate `numInitialChunks` parameter of `shardCollection` command

Closed

Assignee:: Robert Sander
Reporter:: Pierlauro Sciarelli
Participants:: Githook User, Pierlauro Sciarelli, Robert Sander, Sergi Mateo Bellido
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Apr 21 2023 01:24:38 PM UTC
Updated:: Oct 29 2023 09:22:41 PM UTC
Resolved:: Oct 17 2023 03:19:29 PM UTC
Confidence Status Last Update:: 25/Sep/23 8:18 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates