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

Distributed lock manager should not schedule unlock if the lock acquisition did not result in a write

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      If lock acquisition fails for anything other than LockStateChangeFailed, the sharding distributed lock manager will schedule an unlock in order to cleanup any potentially bad leftover state.

      In case of errors, where we know that the lock attempt definitely did not modify any documents, we should not schedule this unlock attempt in order to reduce the amount of logging and mitigate log overflow such as the one described in SERVER-22971.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: