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

sh.enableBalancing() requires an argument, silently no-ops with no argument

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.8.0-rc0
    • 2.5.2
    • Shell, Usability
    • None
    • Minor Change
    • ALL
    • Hide

      mongos> sh.enableBalancing()
      mongos> sh.disableBalancing()

      Show
      mongos> sh.enableBalancing() mongos> sh.disableBalancing()

    Description

      sh.enableBalancing (and disableBalancing) take collection name as an argument. If nothing is passed in, it does not error (probably should!) and then tries to update nobalance flag for collection named "" which of course doesn't exist.

      Since it's easy for a user to assume this command enables/disables global cluster balancing, the no op and no warning or error is somewhat dangerous and misleading.

      Attachments

        Activity

          People

            matt.kangas Matt Kangas
            asya.kamsky@mongodb.com Asya Kamsky
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: