[ioredis] Unhandled error event
See original GitHub issueioredis 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.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:9
Top Results From Across the Web
ioredis Unhandled error event: Error: connect ETIMEDOUT
This is occurring for instantiating only Standalone Redis object in node js. Below is the code I am using, var publisher = new...
Read more >[ioredis] Unhandled error event: Error · Issue #444 - GitHub
The error is very vague [ioredis] Unhandled error event: Error I checked the redis server and it's working fine. var redis = new ......
Read more >ioredis - npm
Sophisticated error handling strategy. Supports NAT mapping. Supports autopipelining. 100% written in TypeScript and official declarations ...
Read more >Heroku won't connect to redis to go [ioredis] Unhandled error ...
Heroku won't connect to redis to go [ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379.
Read more >Laravel-echo-server, Redis and Ubuntu 18.04.4 [ioredis] Error
... connects very fast and after few seconds I start to receive this error in console: [ioredis] Unhandled error event: Error: connect ETIMEDOUT...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi all, I’m having this error quite frequently
🎉 This issue has been resolved in version 4.13.0 🎉
The release is available on:
Your semantic-release bot 📦🚀