[SERVER-59635] Mark ConfigSvrMoveChunkCommand as interruptible on stepdown Created: 27/Aug/21 Updated: 29/Oct/23 Resolved: 17/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.1.0, 5.0.2 |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | 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 | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||
| Sprint: | Sharding EMEA 2021-09-20 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 33 | ||||||||||||||||
| Description |
|
The operation context of ConfigSvrMoveChunkCommand is not currently marked as killable on stepdown. Flagging it as such by calling setAlwaysInterruptAtStepDownOrUp can avoid ending up in deadlocks in case of stepdowns. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 23/Sep/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 7801beb303f43ca38390e9a05cb3dc67bb040c14) |
| Comment by Githook User [ 17/Sep/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |