Primary of shard replica set should update its connection string on the config servers on reconfig

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Sharding
    • None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently any mongos or mongos process monitoring a shard replica set who notices a membership change in the set will attempt to update the config servers. This could lead to a lot of duplicate work. Instead the primary of the replica set being reconfigured should have sole responsibility for updating the config servers.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: