[SERVER-71612] Implement `mergeAllChunksOnShard` in the sharding catalog manager Created: 24/Nov/22 Updated: 29/Oct/23 Resolved: 13/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding EMEA 2022-12-12, Sharding EMEA 2023-01-23 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
It can happen for a shard to own several contiguous sequences of chunks for a given collection. In order to merge them, issuing single merge requests will result in bumping several times the shard version causing frequent routing table refreshes. Purpose of this ticket is to implement a mergeAllChunksOnShard method on the sharding catalog manager that will take care of squashing at once all "mergeable" chunks a shard owns for a given collection and bump the shard versions accordingly. All of that needs to happen in a single transaction. |
| Comments |
| Comment by Githook User [ 13/Jan/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |