[SERVER-43212] Mark MigrationDestinationManager::_migrateThread killable for stepdown Created: 06/Sep/19 Updated: 06/Dec/22 Resolved: 06/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
MigrationDestinationManager::_migrateThread() is not marked killable. We should probably do something like what we did for the range deleter to call setSystemOperationKillable() on the client thread. Otherwise, the migrateThread could be blocked on a prepared transaction for a collection lock (held by a prepared transaction) while holding onto the RSTL, preventing state transition from proceeding. Calling setSystemOperationKillable() will allow stepDown to kill the migrateThread operation. |