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

Implement sh.balancerReset() feature to recover unresponsive balancer control

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Sharding
    • None

    Description

      New feature request, sh.balancerReset() or similar, to avoid the manual labor of attempting control recovery of unresponsive shard balancer conditions.

      Proposed function analyzes the config database for balancer state. If the mongos process listed as having the lock is unresponsive, it should presume that mongos is down and attempt to take the balancer lock itself. If it can, then, it proceeds and tells everyone it has the lock now, etc.

      The goal of this is to fix up situations where issuing a command, sh.stopBalancer() never times-out or error-out, etc. It should be completely fast and deterministic and easy and invisible to most users.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              scott.kurowski@mongodb.com Scott Kurowski
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: