shard replaced, but change only picked up by 1 of 3 config servers

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.6.10
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      A shard "r3" was replaced with a new server (same shard name). One mongos process recognised the change. The second and third mongos processes had a stale picture of which nodes made up rs3.
      Once rs3 was re-added, the balancer (on one of the mongos nodes) started balancing to it's picture of "r3". Remaining two nodes kept looking for the old rs3.

            Assignee:
            Unassigned
            Reporter:
            Annette Morrissey (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: