-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[ioredis] Unhandled error event #896
[ioredis] Unhandled error event #896
Comments
Is this a new bug? Can I use an earlier version? What needs to be done? |
Not sure it is new - but when you clone the listeners when you duplicate the Redis instance I think we will get the right behavior. |
Created PR #899 |
🎉 This issue has been resolved in version 4.13.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I am having this error
|
Long Time no operation will report this error
|
Hi all, I'm having this error quite frequently
|
[ioredis] Unhandled error event: Error: write EPIPE |
can you guys fixed it yet ? |
# [4.13.0](redis/ioredis@v4.12.2...v4.13.0) (2019-07-19) ### Bug Fixes * **cluster:** suppress errors emitted from internal clients ([9a113ca](redis/ioredis@9a113ca)), closes [#896](redis/ioredis#896) [#899](redis/ioredis#899) ### Features * **cluster:** support binary keys ([b414ed9](redis/ioredis@b414ed9)), closes [#637](redis/ioredis#637)
ioredis cluster client will print out connection issues even if I register to error handler.
console.error('[ioredis] Unhandled error event:', error.stack);
Even when your cluster redis instance registered for 'error' or 'node error'.
Look like getInfoFromNode duplicates Redis instance, the current duplicate implementation does not close the event listeners. Any error on the cloned instance will fall to the console.log.
This is an issue as when there are connection problems the process prints out to the console and doesn't trigger the event on the cluster instance.
The text was updated successfully, but these errors were encountered: