[COMPASS-7184] Investigate changes in SERVER-80498: Improve thread safety of ReadConcernArgs modification Created: 04/Sep/23  Updated: 29/Jan/24  Resolved: 29/Jan/24

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Minor - P4
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-80498 Improve thread safety of ReadConcernA... Closed
Epic Link: COMPASS-6403
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

$currentOp output for multi-document transactions used to display the actual readConcern being used. In some cases this could lead to intermittent instances of an operation displaying a different readConcern than the user-provided due to internal operations that temporarily changed it.

With the merged ticket, $currentOp will now display the user-provided readConcern without the possibility of intermittent changes.

Description of Linked Ticket

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 Anna Henningsen [ 29/Jan/24 ]

No discernible impact

Comment by PM Bot [ 04/Sep/23 ]

Fix Version updated for upstream SERVER-80498:
7.2.0-rc0

Generated at Wed Feb 07 22:45:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.