Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5392

Consider allowing only one thread to be responsible in modifying _nodes in ReplicaSetMonitor

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • 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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: