[SERVER-10430] Improve distribution of new chunks when creating hashed sharded collections Created: 04/Aug/13  Updated: 06/Dec/22  Resolved: 14/Jun/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-14394 Create initial chunks directly on shards Closed
is duplicated by SERVER-16715 Distribution of data with hashed shar... Closed
Related
Assigned Teams:
Sharding
Participants:

 Description   

When creating a new hashed collection, it will perform a presplit and move chunks to the other nodes. However, the move chunk command can fail for a couple of reasons:

1. Migration already in progress on the donor.
2. Migration clean up is in progress on the destination shard.

As a result, the initial chunks will be unbalanced. This would mean that the balancer would have to move them later on, which is not ideal since moving chunks of a hashed collection is slow.



 Comments   
Comment by Daniel Pasette (Inactive) [ 19/Aug/13 ]

To actually fix this will require the ability to move multiple chunks at the same time.

Generated at Thu Feb 08 03:23:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.