[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: |
|
||||
| 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: |
| Comment by Githook User [ 08/Jun/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |