[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:
Backports
Depends
is depended on by SERVER-43215 Have a better way to enforce internal... Closed
is depended on by SERVER-43216 Invariant internal operations that ac... Closed
Duplicate
is duplicated by SERVER-43212 Mark MigrationDestinationManager::_mi... Closed
Related
is related to SERVER-70127 Default system operations to be killa... Closed
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: SERVER-43174 Make migration destination threads killable

(cherry picked from commit c4467548514ff07721f4de215b3b74d1111ee9d1)
Branch: v4.2
https://github.com/mongodb/mongo/commit/a20d4b00131c9da1193b213f9fcc49dc9092e6c8

Comment by Githook User [ 13/Sep/19 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@mongodb.com'}

Message: SERVER-43174 Make migration destination threads killable
Branch: master
https://github.com/mongodb/mongo/commit/c4467548514ff07721f4de215b3b74d1111ee9d1

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.

Generated at Thu Feb 08 05:02:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.