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

Remove waiting for balancer lock behavior from sh.startBalancer

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding, Shell
    • None
    • Sharding

      In DOCS-1555 we changed our recommendations for users starting the balancer from using sh.startBalancer() to sh.setBalancerState(true) because the former waits for a mongos to take the balancer lock after enabling the balancer. If we're not recommending that people use sh.startBalancer() because of this behavior, we should probably just remove that behavior so that sh.startBalancer does what we want it to.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: