-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15
The "No more auto-splitter" project eliminated the need for pre-splitting chunks as the balancer is now performing atomic split+move when data need to be moved around.
However, the resharding initial split policy still expects an initial number of chunks that - unless differently specified - is the same number of chunks of the original collection. Purpose of this ticket is to rethink the current approach in order to do not create too many chunks.
- depends on
-
-
- Backlog
-
- is related to
-
-
- In Code Review
-
- related to
-
SERVER-92762 Set default value of numInitialChunks in reshardCollection to 90
-
- Closed
-