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

Automatic removal of stale balancer locks

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible

    Description

      A balancer lock in the config.locks collection might be left after a balancer round interrupt (like mongos shutdown). We need a way to tell if it's just an orphaned record and drop if it is.

      One possible way to detect orphaned balancer lock is to add a "nonce" field to the document, which will be generated on the mongos startup and persist while mongoS is running - it will tie the lock to the specific incarnation of the specific mongos. Then it's balancer process will be able to detect and remove the orphaned lock.

      Attachments

        Activity

          People

            Unassigned Unassigned
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: