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

Metadata freeze command

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Admin, Sharding
    • None
    • Sharding EMEA

    Description

      In sharded clusters some "advanced" maintenance operations like manual chunk rebalancing, performed by DBAs, can benefit from stopping the config metadata changes (i.e. balancer, splits).

      It should be usable, something like sh.freeze() and sh.unfreeze(). Of course, if somebody calls this, they should be ready to handle the implications, e.g. jumbo chunks.

      Currently you can shut down the second or the third config server to achieve the desired effect, but I'm hesitant to call it a solution.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: