Currently the async RedisCluster is managing its own connection pools (see here) which, unlike its synchronous RedisCluster 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 async RedisCluster instance. We also believe that this change might potentially help solve https://github.com/redis/redis-py/issues/2497 .
Would you be open to receiving pull requests for this issue?
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 https://github.com/redis/redis-py/issues/2497 .Would you be open to receiving pull requests for this issue?
Thanks!