Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
None

Sprint:
Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Currently, internal operations rely on calling setSystemOperationKillable() to allow themselves to be killed by the RstlKillOpThread on step up/down. This design is error-prone until we do ~~SERVER-43215~~.

For the time being, we should invariant internal operations that acquire strong locks are marked killable.

depends on

SERVER-43174 Designate the MigrationDestinationManager's migrateThread as system operation killable

Closed

SERVER-44722 3 way deadlock can happen between hybrid index build, prepared transactions and stepdown thread on primary that runs index build via coordinator.

Closed

SERVER-42511 Remove query knob internalQueryUseAggMapReduce

Closed

is related to

SERVER-40936 add an invariant that we do not get a prepare conflict while holding a global, database, or collection MODE_S lock

Closed

SERVER-41034 Invariant if we get a prepare conflict inside runWithoutInterruptionExceptAtGlobalShutdown block.

Closed

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

Closed

related to

SERVER-44779 Invariant internal operations that hit a prepareConflict must be marked killable

Closed

(1 is related to, 1 related to)

Assignee:: Jason Chan
Reporter:: Lingzhi Deng
Participants:: Jason Chan, Lingzhi Deng
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Sep 06 2019 09:38:51 PM UTC
Updated:: Feb 12 2020 03:36:31 PM UTC
Resolved:: Feb 12 2020 03:36:31 PM UTC
Confidence Status Last Update:: 07/Nov/19 3:02 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates