[SERVER-57001] Range deletion snapshotting must always start from a clean state Created: 17/May/21  Updated: 29/Oct/23  Resolved: 18/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-55164 Improve testing around snapshotted ra... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2021-05-31
Participants:
Linked BF Score: 35

 Description   

The snapshotRangeDeletionsForRename function is expecting no snapshotted task to be already associated to the target collection.

As there is currently no machinery in place for incremental range-deletion snapshots, make sure to delete any document that could have been persisted previously (e.g. prior to a stepdown).



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

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-57001 Range deletion snapshotting must always start from a clean state
Branch: master
https://github.com/mongodb/mongo/commit/b4f1a63544d8a1d0e658401e45cda355964dad09

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