[SERVER-64979] Range deleter must start with same range deletion task on step up Created: 28/Mar/22 Updated: 29/Oct/23 Resolved: 13/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18 | ||||
| Participants: | |||||
| Linked BF Score: | 135 | ||||
| Description |
|
Currently, there is no guarantee that range deletions will continue to process the same range after step up that was being processed before step down. This causes a problem for tracking orphaned documents because if an update to the orphan count is missed due to a step down, the document could be processed after all other range deletions, potentially leaving a stale orphan count for a very long time. |
| Comments |
| Comment by Githook User [ 12/Apr/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |
| Comment by Githook User [ 11/Apr/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: Revert " This reverts commit 75f6781664b77b0d4e61f98c61585ac017887bbf. |
| Comment by Githook User [ 07/Apr/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |