[SERVER-5362] ReplicaSetMonitor::notifySlaveFailure not thread safe Created: 22/Mar/12  Updated: 11/Jul/16  Resolved: 31/Mar/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.1.0
Fix Version/s: 2.1.1

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-5110 ReplicaSetMonitor::check not thread s... Closed
Operating System: ALL
Participants:

 Description   

Once you get the index (with respect to _nodes) of the server, it is possible that another thread would refresh _nodes and notifySlaveFailure would end up modifying the wrong node.



 Comments   
Comment by auto [ 31/Mar/12 ]

Author:

{u'login': u'', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-5362 ReplicaSetMonitor::notifySlaveFailure not thread safe
Branch: master
https://github.com/mongodb/mongo/commit/d5cb09f6d92ccbcfab685b7d7c102a5e45a74eda

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