-
Notifications
You must be signed in to change notification settings - Fork 987
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
AbstractRedisClient#shutdown() never ends when Redis is unstable #1768
Comments
Thanks for report. It's a bug in Lettuce where a blocking call happens on a thread that must not be blocked:
|
mp911de
added a commit
that referenced
this issue
Jun 9, 2021
When a cluster node connection fails, we call now the asynchronous closeAsync method instead of the blocking close method.
mp911de
added a commit
that referenced
this issue
Jun 9, 2021
When a cluster node connection fails, we call now the asynchronous closeAsync method instead of the blocking close method.
mp911de
added a commit
that referenced
this issue
Jun 9, 2021
When a cluster node connection fails, we call now the asynchronous closeAsync method instead of the blocking close method.
That's fixed now. |
mp911de
added a commit
that referenced
this issue
Jun 18, 2021
mp911de
added a commit
that referenced
this issue
Jun 18, 2021
mp911de
added a commit
that referenced
this issue
Jun 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Our batch application accesses Redis Cluster with Lettuce 5.1.8.RELEASE.
In our batch application, AbstractRedisClient#shutdown() never ends when Redis is unstable, so the Java process never stops.
From my understanding, shutdown has a timeout parameter (default: 2 sec) to prevent infinite waiting.
It looks the timeout parameter does not work in some cases.
I'm not sure the condition that happen and how to reproduce. But it tends to happen after Redis server fails over and RedisCommandTimeoutException throws.
Current Behavior
The following is a thread dump of calling shutdown. The batch application has been running for a few weeks because of this waiting.
I found an another similar waiting thread.
Environment
The text was updated successfully, but these errors were encountered: