-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
ALL
We should consider waitForWriteConcern as CurOp timer blocked state and exclude it from workingMillis.
Currently, there is at least one instance where wait for write concern overlaps with waiting for locks. We can try moving when the wait for write concern timer starts as conceptually, it should not require locks to achieve write concern.
- is related to
-
SERVER-87914 Re-include waitForWriteConcernMillis in workingMillis
-
- Closed
-