[SERVER-47992] Shard can migrate data on top of orphans if in FCV 4.4 and resumable range deleter was off, then was turned on Created: 06/May/20  Updated: 29/Oct/23  Resolved: 18/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.4.0-rc3
Fix Version/s: 4.4.0-rc7, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Sharding 2020-05-18, Sharding 2020-06-01
Participants:
Linked BF Score: 44

 Description   

If orphans were left on the shard when the shard was in FCV 4.4 and the resumable range deleter was off, then the shard was restarted with the resumable range deleter on, the shard will be able to migrate in data on top of the orphans.

This is because when the resumable range deleter is on, the shard will assume there are no orphans in a range if there are no persistent range deletion tasks that overlap the range.



 Comments   
Comment by Githook User [ 18/May/20 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-47992 Make disableResumableRangeDeleter just prevent ranges from being submitted for deletio
Branch: master
https://github.com/mongodb/mongo/commit/d0e6f87351312a299a17f6d63e3f2f4db834ae1f

Comment by Githook User [ 18/May/20 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-47992 Make disableResumableRangeDeleter just prevent ranges from being submitted for deletion
Branch: v4.4
https://github.com/mongodb/mongo/commit/92f11e326748cdc52ceed072bb15aa83a053c122

Generated at Thu Feb 08 05:15:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.