[SERVER-72283] Take into account mergeability constraints in` mergeAllChunksOnShard` Created: 20/Dec/22 Updated: 29/Oct/23 Resolved: 25/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: |
|
||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Purpose of this ticket is to enhance that method in order to take into account the onCurrentShardSince field introduced by Two or more contiguous non-jumbo chunks belonging to the same collection are going to be considered mergeable when they are owned by the same shard and their history can be safely purged without breaking transactions and snapshot reads. Technically, this means that each chunk to merge is required to fulfill the following conditions:
|
| Comments |
| Comment by Githook User [ 25/Jan/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |