Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Complete
-
4.2.9, 4.3.2
Description
Looks like WATCH doesn't provide good isolation when the call is performed concurrently at the same time from different Threads.
Or we don't use it correctly...
I can simply reproduce it with the @Repeat(10) for the failed test AggregatorWithRedisLocksTests.testDistributedAggregator().
Reconsider locking algorithm as it is recommended by Redis SET command: http://redis.io/commands/set