-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Improve event "node error" to know which node (host+port) of cluster fired it #774
Labels
Comments
luin
added a commit
that referenced
this issue
Feb 3, 2019
luin
added a commit
that referenced
this issue
Feb 3, 2019
🎉 This issue has been resolved in version 4.6.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
janus-dev87
added a commit
to janus-dev87/ioredis-work
that referenced
this issue
Mar 1, 2024
## [4.6.3](redis/ioredis@v4.6.2...v4.6.3) (2019-02-03) ### Bug Fixes * add second arg to "node error" to know which node failed ([#793](redis/ioredis#793)) ([6049f6c](redis/ioredis@6049f6c)), closes [#774](redis/ioredis#774)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
When "node error" event happens on cluster node there is no info in its argument about which node error issued.
I tried to log entire "error" object but there is no info about node. It is important to quickly know host and port of node which has some problems.
The text was updated successfully, but these errors were encountered: