Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.3.10
Affects Version/s: None
Component/s: Internal Code
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 16 (06/24/16), Sharding 17 (07/15/16)
Linked BF Score:
0
Confidence Status:
None
Work Order:
3

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

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

Assignee:: Andy Schwerin
Reporter:: Andy Schwerin
Participants:: Andy Schwerin, Githook User
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Oct 19 2015 01:55:50 PM UTC
Updated:: Jan 25 2017 09:59:48 PM UTC
Resolved:: Jul 14 2016 02:35:33 PM UTC
Confidence Status Last Update:: 17/Jun/16 8:19 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates