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

connect ECONNREFUSED issue #365

Closed
Inter-Dev opened this issue Jan 18, 2013 · 2 comments
Closed

connect ECONNREFUSED issue #365

Inter-Dev opened this issue Jan 18, 2013 · 2 comments

Comments

@Inter-Dev
Copy link

Hi guys,

I use redis with an (redis) sentinel environment.

When one server went away, i still get reconnection messages.

How can i handle unavailable redis instances?

Please explain how to handle with instances who have gone away, can't find any hints in the documentation.

@brycebaril
Copy link
Contributor

I don't believe this library yet supports Redis Sentinel.

I haven't tried yet, but you could consider https://github.com/summerwind/node-redis-sentinel

@DTrejo DTrejo closed this as completed Feb 18, 2013
@BridgeAR
Copy link
Contributor

Either this had nothing to do with node_redis or is fixed now as there should not be any reconnect messages after a failure, since a while back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants