Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Fix
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

For the current code right now, any thread who calls getMaster (and also the ReplicaSetMonitorWatcher) can potentially change the _nodes vector. It is easy for multiple threads to do duplicate work since it is relatively easy for a thread to be replaced by another because it will be blocked when it calls isMaster.

is related to

SERVER-5110 ReplicaSetMonitor::check not thread safe wrt _master

Closed

SERVER-6972 C++ driver should use isMaster, not replSetGetStatus, to monitor health of a replica set

Closed

SERVER-9021 Make sure that at most one thread at a time in mongos is making calls to the shard replSets to update the health of the nodes

Closed

Assignee:: Unassigned
Reporter:: Randolph Tan
Participants:: Eliot Horowitz, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 0 Start watching this issue

Created:: Mar 24 2012 03:16:47 PM UTC
Updated:: Mar 19 2013 04:01:39 PM UTC
Resolved:: Mar 25 2012 02:18:46 AM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates