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

Release distributed locks if shard shuts itself down during a migration

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      If a shard primary purposely shuts itself down during a migration (usually because of a problem communicating with the config servers while in the critical section), we should release all distributed locks while shutting down so that future migrations aren't blocked after the shard recovers (from RS failover and/or by manually bringing the primary back online).

      Attachments

        1. config.log
          826 kB
        2. moveChunk-crash.log
          9 kB

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: