Core
Framework v2.x
2

MutexLockLostError #

Available since 2.57.0

Inherits from the standard JavaScript Error class (not from KuzzleError).

withLock rejects with this error when the lock it holds is lost while its callback is still running, for instance because the lock's TTL could not be extended. Another node may then hold the lock.

The callback itself is not stopped: it keeps running in the background. Do not perform authoritative side effects once this error has been observed.

constructor(key: string, cause?: Error)

ArgumentTypeDescription
key
string
The lost lock's resource identifier
cause
Error
(optional) Why the lock was lost