Uploaded image for project: '[Read Only] - Hippo Repository'
  1. [Read Only] - Hippo Repository
  2. REPO-2006

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • 4.1.2, 4.2.6, 3.2.11, 4.2.7
    • 5.3.1
    • None
    • None
    • 0
    • Turing Sprint 180, Turing Sprint 181

    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

              Unassigned Unassigned
              aschrijvers Ard Schrijvers
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: