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

Uncaught Exception on Zookeeper connection loss #10

Open
hjespers opened this issue Aug 30, 2016 · 2 comments
Open

Uncaught Exception on Zookeeper connection loss #10

hjespers opened this issue Aug 30, 2016 · 2 comments

Comments

@hjespers
Copy link

30 Aug 01:00:44 - [red] Uncaught Exception:
30 Aug 01:00:44 - CONNECTION_LOSS: Exception: CONNECTION_LOSS[-4]
at ConnectionManager.cleanupPendingQueue (/usr/local/lib/node_modules/node-red-contrib-kafka-node/node_modules/kafka-node/node_modules/node-zookeeper-client/lib/ConnectionManager.js:189:46)
at ConnectionManager.onSocketClosed (/usr/local/lib/node_modules/node-red-contrib-kafka-node/node_modules/kafka-node/node_modules/node-zookeeper-client/lib/ConnectionManager.js:274:10)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at TCP._onclose (net.js:486:12)

@mikesparr
Copy link

mikesparr commented Sep 28, 2016

Any update on this? We are experiencing same thing almost daily and we have to slightly move a node in GUI, then redeploy.

Similar issues:

@hjespers
Copy link
Author

I gave up waiting on a fix from the author of node-zookeeper-client and wrote my own node-red-contrib-rdkafka module that uses the librdkafka C/C++ library and the new Kafka 0.9/0.10 client API that doesn't require zookeeper anymore.

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

2 participants