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

Race condition around updating config server connection string and talking to the new node for the first time

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.8
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 9 (09/18/15)
    • 0

      Because the ReplicaSetMonitor (and therefore the Targeter) and the ShardRegistry are decoupled, you may try to target a recently detected CSRS node before it's been added into the config shard in the ShardRegistry, which will cause the ShardingNetworkConnectionHook to fail to establish a connection to it with a ShardNotFound error

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

              Created:
              Updated:
              Resolved: