Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-4248: Refactor RedisLockRegistry

Browse Source 
JIRA: https://jira.spring.io/browse/INT-4248

To avoid unexpected double locking behavior in the cluster,
remove the local cache functionality.

Now with the new `clientId` property, the `expire` for the record in
store is always update on each lock operation
This commit is contained in:
Vedran Pavic
2017-03-31 23:47:27 +02:00
committed by Artem Bilan
parent 28058884f4
commit f7f7bdd067
4 changed files with 347 additions and 532 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/reference/asciidoc/redis.adoc
View File

@@ -764,3 +764,5 @@ Locks are normally held for a much smaller time.
IMPORTANT: Because the keys can expire, an attempt to unlock an expired lock will result in an exception being thrown.
However, be aware that the resources protected by such a lock may have been compromised so such exceptions should be considered severe.
The expiry should be set at a large enough value to prevent this condition, while small enough that the lock can be recovered after a server failure in a reasonable amount of time.
Starting with _version 5.0_, the `RedisLockRegistry` implements `ExpirableLockRegistry` providing functionality to remove locks last acquired more than `age` ago that are not currently locked.