[SERVER-66958] Handle potential multiple "processing" range deletions on step-up Created: 02/Jun/22  Updated: 29/Oct/23  Resolved: 08/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.1, 6.1.0-rc0

Type: Improvement 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:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Sharding EMEA 2022-06-13
Participants:

 Description   

When a range deletion task starts, the relative document is marked as processing so that on step-up we can schedule the same range deletion before all the others.

Changing this if statament with a while would not impact the current semantics but would "protect" from potential bugs that may be introduced in the future, allowing resuming all "processing" deletions (or better, schedule them before all the others).

Even if at moment we don't expect more than one range deletion to be in such state, it would be wise to account for it anyway.



 Comments   
Comment by Githook User [ 22/Jul/22 ]

Author:

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

Message: SERVER-66958 Handle potential multiple "processing" range deletions on step-up
Branch: v6.0
https://github.com/mongodb/mongo/commit/33cc94670994982ca05774d1e79278e81fb44e68

Comment by Githook User [ 08/Jun/22 ]

Author:

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

Message: SERVER-66958 Handle potential multiple "processing" range deletions on step-up
Branch: master
https://github.com/mongodb/mongo/commit/36fd043c358946d78a7fad0d69c1d08deed2790e

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