Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.2.1, 4.3.1
Affects Version/s: 3.6.14, 4.0.12, 4.2.0
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.2
Sprint:
Sharding 2019-09-09, Sharding 2019-09-23
Linked BF Score:
0

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.

is depended on by

SERVER-43215 Have a better way to enforce internal threads that acquire strong locks are killed during step up/down

Closed

SERVER-43216 Invariant internal operations that acquire strong locks are marked killable

Closed

is duplicated by

SERVER-43212 Mark MigrationDestinationManager::_migrateThread killable for stepdown

Closed

is related to

SERVER-70127 Default system operations to be killable by stepdown

Closed

Assignee:: Randolph Tan

Reporter:: Blake Oler

Participants:: Blake Oler, Esha Maharishi, Githook User, Randolph Tan

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: Sep 05 2019 03:15:48 PM UTC

Updated:: Oct 29 2023 10:17:27 PM UTC

Resolved:: Sep 16 2019 02:08:24 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates