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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.7
    • Component/s: Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running rs.reconfig() to remove a node from a replica set, the config servers do not reflect the updated connection string. That is, config.shards is not updated.

              Assignee:
              Unassigned
              Reporter:
              Ben Becker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: