[SERVER-82872] Data race between setParameter and reads of gEnableDetailedConnectionHealthMetricLogLines Created: 07/Nov/23  Updated: 09/Nov/23  Resolved: 09/Nov/23

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

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2
Sprint: Service Arch 2023-11-13
Participants:
Linked BF Score: 131

 Description   

The server parameter gEnableDetailedConnectionHealthMetricLogLines is accessed throughout the codebase in unsynchronized ways, but it can be written to at any time by a setParameter command. We should ensure that all accesses of this parameter are synchronized to avoid data races.



 Comments   
Comment by Githook User [ 08/Nov/23 ]

Author:

{'name': 'Patrick Freed', 'email': 'patrick.freed@mongodb.com', 'username': 'patrickfreed'}

Message: SERVER-82872 Use AtomicWord for gEnableDetailedConnectionHealthMetricLogLines

This fixes a data race between the setParameter command and other reads of
gEnableDetailedConnectionHealthMetricLogLines, which are currently unsynchronized.

Fixes BF-30638.
Branch: master
https://github.com/mongodb/mongo/commit/0f16443b3f323f021a9510fcd802f4b7a1973886

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