[DOCS-16446] Investigate changes in SERVER-76405: Reduce the initial minimum number of chunks to 1 per shard for empty collections with hashed shard key Created: 18/Oct/23 Updated: 13/Nov/23 Resolved: 09/Nov/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, Server_Docs_20231113 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Sarah Simpers |
| Resolution: | Done | Votes: | 0 |
| Labels: | request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 16 weeks, 1 day ago | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Original Downstream Change Summary Reduced the initial minimum number of chunks to 1 per shard for empty collections with hashed shard key Description of Linked Ticket 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 ( 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). |