-
Notifications
You must be signed in to change notification settings - Fork 19
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
EPIPE error #49
Comments
I'm also facing this issue, fixed it by using TedisPool instead and My assumption is that the single tedis client is used by multiple clients(your app), and causes the socket to be closed immaturely. |
We are also facing the similar issue on
|
I have this problem, too |
Has anyone found a solution to this problem? |
This issue seems to be associated with connection pool. In our case, we had lot of services connected to Redis and some of the services went offline due to application failure (exceptions were thrown). |
Definitely, this error is not associated with the pool. On the contrary, I replaced my connection for use pools and now it works perfectly. |
Has someone solved this issue? |
getting following error: This socket has been ended by the other party
The text was updated successfully, but these errors were encountered: