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

Provide feedback to RemoteCommandTargeter on NotMaster errors

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 7 08/10/15

      Everywhere that uses the RemoteCommandTargeter to talk to replica sets for PrimaryOnly operations needs to be prepared to receive a NotMaster response. Currently DBClientReplicaSet feeds information back into the ReplicaSetMonitor when it receives NotMaster responses so the monitor knows to refresh its view of the who the current primary is. We need to duplicate this logic when using the RemoteCommandTargeter.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: