Closed mariaines closed 2 years ago
+1
@mariaines How did you end up proceeding? redis-py-cluster looks like a potential alternative but its not asyncio.
We are still on this library, the ConnectionResetError are infrequent enough that it's been fine for us. That said we are still thinking about just moving to redis-py / redis-py-cluster and accepting the lack of async.
Are you sure the problem is with aioredis and not with the number of connections on redis node? Check connected_clients
and rejected_connections
in INFO
command output. Also check maxclients
config option if connected_clients
near on this limit. Also make sure you have enough network resources (number of ports, limits, TCP_NOWAIT states, etc.) on the client host and redis itself.
ConnectionResetError usually means network level problems. this is in fact receive of the RST packet.
And answer the question. There are no plans to migrate to aioredis>=2
.
Hi, are there any plans to migrate to aioredis 2.0.0?
I am running into occasional ConnectionResetError and this issue suggests 2.0.0 might fix it (maybe...)