Uploaded image for project: 'Hippo Repository'
  1. Hippo Repository
  2. REPO-1990

Lock manager unable to reclaim lock, because expire time still gets updated for 'running' jobs that no longer exist

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 4.1.2, 4.2.6, 4.2.7, 3.2.12
    • Fix Version/s: 5.4.0
    • Labels:
      None
    • Similar issues:
    • Story Points:
      1
    • Sprint:
      Turing Sprint 180, Turing Sprint 181
    • Processed by team:
      Turing

      Description

      When a cluster node has an active lock and is shutdown without releasing the lock. It's possible that the lock can't be reclaimed, whenever this server is up and running within the time that the lock should expire. When the server is up and running, the server keeps updating the expire time of the lock, while there is actually no process running.

      The result is that no server is able to claim te lock, because the expire time will 'never' expire.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dvandiepen Dirkjan van Diepen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: