[SERVER-77984] Make ElapsedTracker non-thread safe Created: 12/Jun/23  Updated: 29/Oct/23  Resolved: 22/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Mark Benvenuto Assignee: Mark Benvenuto
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
Sprint: Security 2023-06-26
Participants:
Linked BF Score: 4

 Description   

ElapsedTracker is used in two situations
1. By PlanYieldPolicy as part single-threaded queries to determine if they should yield
2. By WiredTigerKVEngine to track if the sizeStorer should be flushed

Only the second case needs to be thread-safe. This can be done with a mutex instead of using atomics in all cases.



 Comments   
Comment by Githook User [ 21/Jun/23 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-77984 Make ElapsedTracker non-thread safe
Branch: master
https://github.com/mongodb/mongo/commit/ae7d530fcd97a513eaa87eea5afc94750e8fed94

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