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

The sh.setBalancerState(false) command returns a misleading result on shard mongods

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 3.1.8
    • Affects Version/s: 2.6.3
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Hide

      Follow our docuemented procesdures in http://docs.mongodb.org/manual/reference/method/sh.setBalancerState/

      Apply this to a mongod.

      Show
      Follow our docuemented procesdures in http://docs.mongodb.org/manual/reference/method/sh.setBalancerState/ Apply this to a mongod .
    • Build 8 08/31/15

      The documented approach to stopping the shard balancer is to use the "sh.setBalancerState(false)" command on the mongos. However the command can also be run on any mongod, and no exception is raised.

      This is because the the command successfully writes to the local config, but this is nonsensical on a mongod. This can mislead the user into thinking the command has given the desired result.

      This server request is to add some exception handling to help prevent this confusion.

            Assignee:
            sam.kleinman Sam Kleinman (Inactive)
            Reporter:
            luke.prochazka@mongodb.com Luke Prochazka
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: