yangkangquan123

Results 5 comments of yangkangquan123

Redisson concurrent locking may occasionally cause one of the threads to acquire a timeout, resulting in lock failure

> Make sure that it's not the same thread. Since the lock is reentrant. Not the same thread, because two concurrent requests are sent to different nodes, it is impossible...

Redisson concurrent locking may occasionally cause one of the threads to acquire a timeout, resulting in lock failure

> My question is that before the second thread subscribes, the first thread has already released the lock and published the event of releasing the lock. Will the second thread...

Redisson concurrent locking may occasionally cause one of the threads to acquire a timeout, resulting in lock failure

Perhaps it's not the reason for this code. Today, we tested in a testing environment and applied for locks on 10000 locks simultaneously within one minute, with each lock being...

Redisson concurrent locking may occasionally cause one of the threads to acquire a timeout, resulting in lock failure

Our locking code is roughly like this: `RLock lock = redissonClient.getReadWriteLock(key).writeLock(); boolean lockSuccess = lock.tryLock(waitTime, LEASE_TIME, TimeUnit.MILLISECONDS);`

Redisson concurrent locking may occasionally cause one of the threads to acquire a timeout, resulting in lock failure

> If it's subscribed after the event was published then it won't get a notification. I don't see the reason of continuous blocking here. Another phenomenon is that the log...