Fixed lockd infinetely trying to unlock a crashed client's lock

Detail name	Value
Changelog Number	23137
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.0.0
Fix Versions	Exasol 8.29.10, Exasol 2025.1.0
Resolution Date	2025-05-15

Description

If the locking service, also known as lockd, was unsynchronized and a client crashed, lockd would attempt to unlock the crashed client’s locks and would fall into an infinite loop trying to unlock the locks. The loop would produce huge amounts of logs that would fill up the disk very quickly. The loop would also result in a lot of events sent to all the nodes that would also increase the networking load on the nodes.

Workaround

There are no workarounds.

Fix

If lockd is unsynchronized, lockd will now defer the unlock request for later and will handle it as soon as it is synchronized again.