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

distributed lock should be forceable if no lock documents exist on some servers

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      This should be fairly rare, since lock documents generally exist after the first lock attempt, but is something that could prevent balancing progress in a cluster, for example. The lock document on the first config server is forced, and state set to 0, but on subsequent lock attempts the lock tournament step fails because contacting the second or third config server results in an empty document which we don't handle correctly.

      Needs a simple reproduction case. Seems possible from a code audit.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: