Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5896

Server removed from replica set in sharded cluster is not fully removed

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 2.0.4
    • Replication, Sharding
    • None
    • Sharded Linux cluster:
      3 config servers
      3 shards, each (initially) with three nodes per shard (reconfigured to two nodes and an arbiter)
      1 mongos
    • Linux

    Description

      A sharded cluster was reconfigured to replace a secondary on each of the three shards with an arbiter. This appeared to work based on command responses and acknowledgements in the logs, but the mongos continued to try to add the removed secondary back in, even after being restarted more than once. The mongos log showed a loop of erasing and then re-adding the removed node. The cluster did not become usable again until the removed nodes were added back to the cluster. Restarting the config servers did not help. We did not try restarting the individual nodes.

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            tad Tad Marshall
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: