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

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.1.8
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 9 (09/18/15)
    • 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

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-20294 Race condition in shard targeting logic results in "Shard not found" error

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-19608 Send shard initialization data when talking through NetworkInterface

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: