[SERVER-76136] Shard Collection to Automatically Distribute Chunks for an Empty Collection when Customer Provides Split Points Created: 14/Apr/23  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: 7.0.0-rc0, 6.0.5
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Matt Panton Assignee: Robert Sander
Resolution: Unresolved Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-84807 Fix wrong pre-splitting documentation... Open
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
Participants:
Story Points: 3

 Description   

With the introduction of the new balancing algorithm in 6.0.3 balance is determined by data size per (sharded) collection per shard. This had the knock-on effect of changing the steps to execute the commonly used tactic of splitting an empty collection to maximize throughput when inserting data into a cluster.

Customers should be provided a way to provide their desired split points for their empty collection and then have the appropriate ranges automatically migrated to the other shards of the cluster.



 Comments   
Comment by Cris Insignares Cuello [ 12/May/23 ]

I: 2
E: 3

Generated at Thu Feb 08 06:31:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.