-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Concurrency, Storage
-
None
-
Fully Compatible
-
v3.6
-
Storage 2018-02-12, Storage NYC 2018-03-12
-
(copied to CRM)
-
5
Currently, a dblock acquisition for a contended resource is not interruptable by killOp; the thread will wait indefinitely until the lock is granted.
This is not normally a problem, as most locks are held for short periods of time (except for foreground index builds). However, the design of multi-statement transactions will allow locks to be held for long periods of time in more cases. In such situations, it will be important to have the ability to kill operations that are waiting for locks to be granted.
This applies to global, database, and collection-level locks.
- causes
-
SERVER-33927 The NoopWriter is not resilient to `InterruptedAtShutdown` exception.
- Closed
-
SERVER-34616 second index build interrupt crashed mongod
- Closed
- is depended on by
-
SERVER-34616 second index build interrupt crashed mongod
- Closed
- related to
-
SERVER-49305 Remove reconfig retries in our tests
- Closed