-
Notifications
You must be signed in to change notification settings - Fork 147
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
ConnectionManager infinite connect retries #30
Comments
tekny
changed the title
ConnectionManager infinite connection retries
ConnectionManager infinite connect retries
Nov 26, 2014
+1 |
+1 as well. |
+1 |
Bump! |
+1 |
hufeng
pushed a commit
to hufeng/node-zookeeper-client
that referenced
this issue
Apr 17, 2015
+1 |
+1 |
2 similar comments
+1 |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In case server is offline,
ConnectionManager
will try to reconnect infinite times without emitting errors or any other notifying. Because of that innode-kafka
which usesConnectionManager
it's impossible to handle connection errors. It also goes 100% CPU (I guess because of retries frequency) with node 10.30 OS X. It doesn't consume all the CPU on 10.33, but connection loss is still unmanageable.Can we have those errors emitted or fixed retries count or something else.
The text was updated successfully, but these errors were encountered: