[SERVER-70296] Serialize concurrent access to CurOp dataThroughputLastSecond and dataThroughputAverage metrics Created: 06/Oct/22  Updated: 29/Oct/23  Resolved: 06/Oct/22

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

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
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: Execution Team 2022-10-17
Participants:
Linked BF Score: 15

 Description   

CommonProcessInterface::getCurrentOps() already locks the client before retrieving the CurOp report. The throttle cursor does not. We should lock the client in the throttle cursor prior to updating CurOp.



 Comments   
Comment by Githook User [ 06/Oct/22 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-70296 Serialize concurrent access to CurOp dataThroughputLastSecond and dataThroughputAverage metrics
Branch: master
https://github.com/mongodb/mongo/commit/8e586bf05d76dd3bfb91a1f536c4ef32f40c3078

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