-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Repl 2023-05-01, Repl 2023-05-15
-
35
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Field waitForWriteConcernDurationMillis in OpDebug is able to be accessed twice. Once by reportState (for reporting currentOp) and once when finishing waiting for write concern. The solution here should be to use another atomic variable to keep track of current duration in ticks and then only convert to and use the millis duration for use in slow query