Skip to content
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

Open
pratyush-sngh opened this issue Jul 5, 2020 · 7 comments
Open

EPIPE error #49

pratyush-sngh opened this issue Jul 5, 2020 · 7 comments
Labels
bug Something isn't working

Comments

@pratyush-sngh
Copy link

getting following error: This socket has been ended by the other party

@surapich
Copy link

surapich commented Aug 13, 2020

I'm also facing this issue, fixed it by using TedisPool instead and getTedis every time I need to interact with redis, and putTedis back when done.

My assumption is that the single tedis client is used by multiple clients(your app), and causes the socket to be closed immaturely.

@samundra
Copy link

samundra commented Nov 2, 2020

We are also facing the similar issue on Tedis. We still think it is due to high load on Redis server. We are also not using connection pool.

error: { Error: This socket has been ended by the other party
    at Socket.writeAfterFIN [as write] (net.js:393:12)
    at /partner/node_modules/tedis/build/core/base.js:83:26
    at new Promise (<anonymous>)
    at Tedis.Base.command (/partner/node_modules/tedis/build/core/base.js:78:16)
    at Tedis.<anonymous> (/partner/node_modules/tedis/build/api/string.js:122:55)
    at step (/partner/node_modules/tedis/build/api/string.js:46:23)
    at Object.next (/partner/node_modules/tedis/build/api/string.js:27:53)
    at /partner/node_modules/tedis/build/api/string.js:21:71
    at new Promise (<anonymous>)
    at __awaiter (/partner/node_modules/tedis/build/api/string.js:17:12) code: 'EPIPE' }

@dasoncheng dasoncheng added the bug Something isn't working label Nov 3, 2020
@lxjcxj
Copy link

lxjcxj commented Jan 4, 2021

I have this problem, too

@leandromatos-hotmart
Copy link

Has anyone found a solution to this problem?

@samundra
Copy link

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).

See Tedis Conenction Pooling

@leandromatos-hotmart
Copy link

Definitely, this error is not associated with the pool. On the contrary, I replaced my connection for use pools and now it works perfectly.

@IvchaZGB
Copy link

IvchaZGB commented Feb 4, 2021

Has someone solved this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants