Race in ShardRegistry::reload and config.shard update can cause shard not found error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.2.3, 3.3.0
    • Affects Version/s: 3.2.0
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • Sharding E (01/08/16)
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The ReplicaSetMonitor monitors membership changes of all the known replica set shards in mongos and tries to update the ShardRegistry and config.shards. The issue is that when the ShardRegistry::reload gets called, it will clear all it's entries and tries to reread the contents from config.shards. So there is a small window were the ShardRegistry 'forgets' the newly added replSet member until config.shards get updated and reload gets called again.

              Assignee:
              Misha Tyulenev (Inactive)
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: