-
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
Connection error not thrown when Sentinel master name is wrong #397
Comments
Check out |
@luin yeah, I can see retries happening - but how can I get error message? |
Yes, an |
Hmm, error message is |
That's strange. How many sentinels do you have? Given ioredis only emits the last error (https://github.com/luin/ioredis/blob/5f740758593bb0e2342d25c1f84e43418d6cb868/lib/connectors/sentinel_connector.js#L78-L79), it seems ioredis tried to connect to another sentinel and got |
I have the following config:
And I think that error message should be the same for both sentinels since |
Could you post full logs here including retries for the two sentinels? |
Yeah, here is the last retry attempt (99 of 100): ioredis:SentinelConnector All sentinels are unreachable. Retrying from scratch after 99 +1ms |
It shows |
Oops. My bad. Sentinel really listened only on 26379. Stupid mistake, sorry for taking your time. Thank you very much! |
Hi! I happened to have a wrong master
name
in my config. ioredis kept reconnecting and didn't throwerror
event. If I enable debug mode, I can see error:But how can I catch it in my application?
P.S. using ioredis v 2.4.0
The text was updated successfully, but these errors were encountered: