-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add idleBetweenTries property to RedisLockRegistry #9540
Labels
Milestone
Comments
Ichanskiy
added
status: waiting-for-triage
The issue need to be evaluated and its future decided
type: enhancement
labels
Oct 8, 2024
Ichanskiy
pushed a commit
to Ichanskiy/spring-integration
that referenced
this issue
Oct 8, 2024
artembilan
added
in: redis
and removed
status: waiting-for-triage
The issue need to be evaluated and its future decided
labels
Oct 8, 2024
artembilan
pushed a commit
that referenced
this issue
Oct 8, 2024
Ichanskiy
pushed a commit
to Ichanskiy/spring-integration
that referenced
this issue
Oct 9, 2024
Ichanskiy
pushed a commit
to Ichanskiy/spring-integration
that referenced
this issue
Oct 9, 2024
artembilan
pushed a commit
that referenced
this issue
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hello,
We are using
RedisLockRegistry
in our project and noticed that, there is a Redis query every 100 milliseconds to check for the lock:The issue is that we can't configure the sleep duration between these requests (
Thread.sleep(100); //NOSONAR
), resulting in a large number of Redis requests.In
JdbcLockRegistry
, there is a similar property, idleBetweenTries, that allows this configuration.My suggestion is to add a similar configuration option for
RedisLockRegistry
. Specifically:private Duration idleBetweenTries = Duration.ofMillis(DEFAULT_IDLE);
idleBetweenTries
in thetryRedisLockInner()
method:The text was updated successfully, but these errors were encountered: