Update sh.enableBalancing and sh.disableBalancing to use configureCollectionBalancing

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 2
    • Needed
    • Hide

      This will need to make us revisit DOCSP-45929 – while the shell commands did not previously work on Atlas clusters, they now (likely) will on Atlas clusters with a sufficiently recent version – ones which have SERVER-78849 and ones to which that ticket get backported to (possibly 8.0, see BACKPORT-23839).

      Show
      This will need to make us revisit DOCSP-45929 – while the shell commands did not previously work on Atlas clusters, they now (likely) will on Atlas clusters with a sufficiently recent version – ones which have SERVER-78849 and ones to which that ticket get backported to (possibly 8.0, see BACKPORT-23839).
    • Developer Tools

      sh.enableBalancing and sh.disableBalancing allow customer to enable and disable balancing for a specific namespace respectively. This is done by executing a write to config.collections. For Atlas customers updates to the config namespaces except for config.settings are disabled meaning that customers cannot enable or disable balancing on a namespace level outside of a workaround of misusing command such as setAllowMigrations. 

      In MongoDB 8.1, the server has updated the configureCollectionBalancing command to allow customers to enable and disable balancing via the command which internally updates config.collections. 

       

      It would be best if sh.enableBalancing and sh.disableBalancing were modified to interact with configureCollectionBalancing instead of issuing a direct write to the config server. 

            Assignee:
            Nikola Irinchev
            Reporter:
            Matt Panton
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: