[SERVER-43174] Designate the MigrationDestinationManager's migrateThread as system operation killable Created: 05/Sep/19 Updated: 29/Oct/23 Resolved: 16/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.14, 4.0.12, 4.2.0 |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Randolph Tan |
| 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: |
v4.2
|
||||||||||||||||||||||||||||||||
| Sprint: | Sharding 2019-09-09, Sharding 2019-09-23 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||||||||||
| Description |
|
Currently, the migrateThread is not designated as system operation killable. This means that a stepdown will skip killing the migration, which could lead to a deadlock as seen in the linked BF. The solution is easy – add this line as seen with the range deleter to the migrateThread here. |
| Comments |
| Comment by Githook User [ 08/Oct/19 ] |
|
Author: {'email': 'randolph@mongodb.com', 'name': 'Randolph Tan'}Message: (cherry picked from commit c4467548514ff07721f4de215b3b74d1111ee9d1) |
| Comment by Githook User [ 13/Sep/19 ] |
|
Author: {'name': 'Randolph Tan', 'email': 'randolph@mongodb.com'}Message: |
| Comment by Esha Maharishi (Inactive) [ 09/Sep/19 ] |
|
Assigning to renctan, since it is a deadlock we introduced in 4.2 and should backport ASAP. |