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

balancer won't start until all shards are reachable once

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.4.0-rc2
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The balancer does an OID check to determine if all shards are unique processes, but this check happens before it starts and requires all shards be reachable at the same time. After that time, the balancer will act as usual. A cluster should to function well even when partially unavailable when mongos starts, so we should at least remember which hosts we've contacted already successfully and not retry those hosts, or better, allow migrations between hosts that we know are fine.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            greg_10gen Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: