[SERVER-80498] Improve thread safety of ReadConcernArgs modification Created: 29/Aug/23  Updated: 29/Oct/23  Resolved: 04/Sep/23

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by COMPASS-7184 Investigate changes in SERVER-80498: ... Closed
Documented
is documented by DOCS-16365 [SERVER] Investigate changes in SERVE... Closed
Related
related to SERVER-78952 Revert SERVER-78855 after SERVER-77506 Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.1
Sprint: Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18
Participants:
Linked BF Score: 5

 Description   

There is a harmless race between a thread performing an operation using DBDirectClient that temporarily resets the ReadConcernArgs (example) and the currentOps method reading the ReadConcernArgs of the target operation (code).

The main risk potential for this is an operation printing potentially wrong information for the read concern used. This would occur if the currentOp thread acquired a copy of the data while the temporary reset was happening.



 Comments   
Comment by Githook User [ 04/Sep/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-80498 Make a copy of ReadConcernArgs for monitoring at the start of a transaction
Branch: master
https://github.com/mongodb/mongo/commit/c5f834a1b13c2081164a06fa34ae62dba4202f6f

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