[SERVER-26661] Add option for shardCollection to wait for initial chunks to be balanced Created: 13/Oct/16 Updated: 06/Dec/22 Resolved: 15/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Steven Hand | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Done | Votes: | 0 |
| Labels: | chunking, etl, sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Sprint: | Sharding 2016-12-12, Sharding 2017-01-02 |
| Participants: |
| Description |
|
This is useful for sharding huge collections and the user would want to wait for the collection to be in steady state before inserting new documents. Note: for empty collections, the chunks should already be balanced when the shardCollection command returns successfully. Original description
|
| Comments |
| Comment by Kaloian Manassiev [ 15/Nov/21 ] |
|
Most of the requests in this ticket have been done under |
| Comment by Steven Hand [ 21/Oct/16 ] |
|
Of course they could query the config database collections directly. Regardless, of how the data is collected, without the proposed change, the customer would have to calculate when the collection is balanced in order to avoid the adverse side-effects in this scenario. |
| Comment by Asya Kamsky [ 13/Oct/16 ] |
|
are they doing "shardCollection" and giving it some huge number of chunks? If so why? They shouldn't be. |