[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:
Depends
depends on SERVER-71612 Implement `mergeAllChunksOnShard` in ... Closed
depends on SERVER-71615 Add top-level `onCurrentShardSince` f... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
Participants:

 Description   

SERVER-71612 introduced a catalog manager method merging in one-shot contiguous sequences of chunks for a given collection for a given shard.

Purpose of this ticket is to enhance that method in order to take into account the onCurrentShardSince field introduced by SERVER-71615 and the jumbo flag.

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: SERVER-72283 Take into account mergeability constraints in` mergeAllChunksOnShard`
Branch: master
https://github.com/mongodb/mongo/commit/798c8f3d8a7ae1e3265deda179b6b5bf0baf330c

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