[SERVER-76676] Concurrent access of waitForWriteConcernDurationMillis in OpDebug Created: 28/Apr/23  Updated: 29/Oct/23  Resolved: 03/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Sean Zimmerman Assignee: Sean Zimmerman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2023-05-01, Repl 2023-05-15
Participants:
Linked BF Score: 35

 Description   

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



 Comments   
Comment by Githook User [ 03/May/23 ]

Author:

{'name': 'seanzimm', 'email': 'sean.zimmerman@mongodb.com', 'username': 'seanzimm'}

Message: SERVER-76676: Concurrent access of waitForWriteConcernDurationMillis in OpDebug
Branch: master
https://github.com/mongodb/mongo/commit/0eeb3eba4d8340788adad30064dfe2ec79c891db

Comment by Sean Zimmerman [ 01/May/23 ]

Running TSAN patch build now to verify the fix worked

Generated at Thu Feb 08 06:33:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.