-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
Sharding 16 (06/24/16), Sharding 17 (07/15/16)
-
0
Operations running in MongoDB often have soft time limits and all are intended to be interruptible at certain interruption points. Today, this is done in an ad hoc manner using bare std::condition_variable to wait for application events. Checking for interruption or the expiration of the maxTimeMs time limit is done on an ad hoc basis, and sometimes omitted.
This task is to build new condition variable wait methods that take an OperationContext, and support operation killing and maxTime expiration.
- is related to
-
SERVER-21118 A slaveDelay'd member in sleep gets stuck in shutdown
- Closed
-
SERVER-4984 make it possible to interrupt operations in mongos
- Closed
-
SERVER-25062 Implement interruptible sleep and condition variable waitFor methods on OperationContext
- Closed
- related to
-
SERVER-27345 reclaim inactive WT sessions on calling closeAllCursors
- Closed