[SERVER-70094] Synchronize shutdown with resuming of range deletions Created: 29/Sep/22 Updated: 29/Oct/23 Resolved: 29/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | 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 | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2022-10-03 | ||||||||
| Participants: | |||||||||
| Description |
|
On step-up, range deletion tasks are recovered from disk by spawning a thread that is asynchronously taking care of registering tasks on the service in order to avoid blocking the transition to primary. Since tasks registration requires the acquisition of the service lock, it's needed to synchronize the resuming with shutdown that acquire the same mutex and may deadlock when trying to join the executor the resume is scheduled on. |
| Comments |
| Comment by Githook User [ 29/Sep/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |