-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Use a blocking connection pool in the async RedisCluster instead of managing connections synchronously #2522
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
Comments
Any updates? We'd be more than happy to work on this implementation. |
This issue is marked stale. It will be closed in 30 days if it is not updated. |
I'd also find this useful! Not stale. |
This issue is marked stale. It will be closed in 30 days if it is not updated. |
The stale label was removed by mistake, but since the 30 days have almost passed, I'm closing this issue now (the automated process would close it in a few days). |
Version:
redis-py
version 4.4.0Platform: N/A
Description:
Currently the async
RedisCluster
is managing its own connection pools (see here) which, unlike its synchronousRedisCluster
counterpart which is managing its connections by using the implementations of the Connection Pools that are available (see here). We currently have a use case where we'd much prefer to be using blocking connection pools and would be happy to work on such a change for the asyncRedisCluster
instance. We also believe that this change might potentially help solve #2497 .Would you be open to receiving pull requests for this issue?
Thanks!
The text was updated successfully, but these errors were encountered: