-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Question: When do released connections expire? #445
Comments
Typically I've seen this handled by setting an idle timeout on the server. However, you could likely implement a custom ConnectionPool that close idle connections after a bit of time. |
Thanks Andy! Do connections waiting for blpop count as idle on the server? |
Using the following modified ConnectionPool to evict idle connections.
|
Looks like that'll do it. Feel free to re-open if you need anything else. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We get very infrequent bursts of redis connection requests, and what that does is that the number of connections to the Redis server to go up but stay there indefinitely. I didn't see anything in the code that cleans up such connections.
What is the best way to get rid of such released idle connections within a timeout without setting a client timeout on the server?
Appreciate the help
The text was updated successfully, but these errors were encountered: