-
Notifications
You must be signed in to change notification settings - Fork 992
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
RedisClient.shutdown hangs because event loops terminate before connections are closed #998
Comments
Thanks a lot for tracking down this issue. The solution would be to await closing of the resources first and then shutting down event loops. |
Poorva17
added a commit
to tmtsoftware/csw
that referenced
this issue
Mar 12, 2019
Lettuce-core 5.1.5 has bug redis/lettuce#998. This is fix for bug.
mp911de
changed the title
RedisClient.shutdown hangs after upgrade to 5.1.5
RedisClient.shutdown hangs because event loops terminate before connections are closed
Mar 14, 2019
mp911de
pushed a commit
that referenced
this issue
Mar 14, 2019
ClientResources are released after awaiting channel close completion to avoid event loop termination before the channels had a chance to get closed. Co-authored-by: Pritam Kadam <[email protected]> Original pull request: #1000.
mp911de
pushed a commit
that referenced
this issue
Mar 14, 2019
ClientResources are released after awaiting channel close completion to avoid event loop termination before the channels had a chance to get closed. Co-authored-by: Pritam Kadam <[email protected]> Original pull request: #1000.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current Behavior
RedisClient.shutdown hangs after upgrade to 5.1.5 from 5.0.5
Input Code
Expected behavior/code
RedisClient should shutdown gracefully.
Environment
Possible Solution
While comparing shutdown implementation with 5.0.5 and 5.1.5 we see following change in 5.1.5
Shutdown creates multiple futures e.g. closeableResources.closeAsync , channels.close, clientResources.shutdown. These futures will run concurrently which means in some cases event loop can get shutdown before closing channels or other resources which could cause this exception.
Additional context
We are getting following exception
This works fine with Lettuce version(s): [e.g. 5.0.5.RELEASE or lower versions].
The text was updated successfully, but these errors were encountered: