[SERVER-47831] numAwaitingTopologyChanges metrics must be changed under ReplicationCoordinator mutex Created: 29/Apr/20  Updated: 29/Oct/23  Resolved: 05/May/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.5 Required, 4.4.0-rc3
Fix Version/s: 4.4.0-rc4, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Repl 2020-05-18
Participants:

 Description   

The numAwaitingTopologyChanges metric is update outside of the ReplicationCoordinator mutex here. This metric must be updated under the mutex in order to synchronize with resetting the metric to zero.



 Comments   
Comment by Githook User [ 06/May/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-47831 numAwaitingTopologyChanges metrics must be changed under ReplicationCoordinator mutex

(cherry picked from commit 9e80c5c46ec01e61e020681b393ce8e529049836)
Branch: v4.4
https://github.com/mongodb/mongo/commit/ee4469deb65a32870f27694be255762ec183266b

Comment by Githook User [ 05/May/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-47831 numAwaitingTopologyChanges metrics must be changed under ReplicationCoordinator mutex
Branch: master
https://github.com/mongodb/mongo/commit/9e80c5c46ec01e61e020681b393ce8e529049836

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