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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.8
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 9 (09/18/15)
    • Linked BF Score:
      0

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: