mongos doesn't always update shards in response to replica set changes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.0.3, 2.1.0
    • Affects Version/s: 2.0.2, 2.1.0
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      when adding or removing a member from a replica set via a reconfig, mongos does not always update the config.shards collection. Seems to update on startup, but not on general reconfig.
      Test case reproduces.

        1. mongos_no_replica_set_refresh.js
          1 kB

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: