You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that connections are not being closed correctly when the connection is "lost". I first noticed this when redis stopped taking in new connections and had reached it's maximum connections and I had to restart my app.
I am not able to reliable make the protocol think that the connection is lost, however when it does it is clear that the number of connections grows. I am watching the connections with netstat | grep 6379 | wc -l on a server that only has this once instance of the app. Right after the logs print out Redis connection lost I see that it has grown by 20 connections (pool size of 5 with 4 processes).
The text was updated successfully, but these errors were encountered:
@mackeyja92 Did you find any workaround?
I have same problem, after first test there are no awardable connections.
My workaround for now - add try-except where I'm using redis:
It appears that connections are not being closed correctly when the connection is "lost". I first noticed this when redis stopped taking in new connections and had reached it's maximum connections and I had to restart my app.
I am not able to reliable make the protocol think that the connection is lost, however when it does it is clear that the number of connections grows. I am watching the connections with
netstat | grep 6379 | wc -l
on a server that only has this once instance of the app. Right after the logs print outRedis connection lost
I see that it has grown by 20 connections (pool size of 5 with 4 processes).The text was updated successfully, but these errors were encountered: