-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
-
Fully Compatible
-
ALL
-
Programmability 2025-08-04, Programmability 2025-08-18
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
There is some work that is done on the command path prior to setting the deadline on the opCtx which could potentially have non-trivial latency (e.g. mutex acquisition, see SERVER-99896 and HELP-68909). If this work takes a sufficiently long amount of time, then the user's maxTimeMS will not be respected. We should set the deadline as early as possible, ideally before acquiring any kind of mutex that might have contention on it, to ensure that our deadline is as close to what the user intended as possible.
- is related to
-
-
- Open
-
- related to
-
SERVER-99896 Consider making opLatency metrics more comprehensive
-
- Open
-
-
-
- Closed
-