-
Notifications
You must be signed in to change notification settings - Fork 986
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 sometimes #2278
Comments
The threads do not indicate a deadlock so I'm not able to tell from these details what's going on. |
Is there any other input for this investigation? I will replace |
From #1768, I have the same problem, Lettuce version: 6.2.2.RELEASE, the jstack show:
|
Please include the full stack trace. There must be other threads involved blocking something on what the shutdown synchronizes. |
@mp911de full stack trace: |
Interesting, there are no live netty threads anymore. Did you observe any error log output? |
There are no other errors, the cpu is normal, the thread status in my thread pool is WAITING. |
using 6.1.8.RELEASE and hitting the similar trace as @yangbodong2201.(using vertx-core 3.9.4 - not sure if this matters) Application has hundreds of Vertx I find this interesting because other
|
This is happening to me as well. The thread dump has the shutdownhook in a WAITING state, with several lettuce threads afterwards in a TIMED_WAITING state.
|
FYI: eventually I used |
Bug Report
Our application accesses Redis Cluster with Lettuce 6.1.5.RELEASE.
AbstractRedisClient#shutdown() never ends sometimes, so the threads are never released.
It looks similar to #1768 that I reported last year, but the stack trace is a little different.
Current Behavior
The following is a thread dump of calling shutdown.
Lettuce threads.
Environment
The text was updated successfully, but these errors were encountered: