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

An unhandled rejection triggered , when kafka-node can not connect to the broker. #974

Open
yunnysunny opened this issue May 15, 2018 · 0 comments

Comments

@yunnysunny
Copy link

Bug Report

We use kafka.KafkaClient to init a client, and listen the event of error to catch the error of the client. But something may not pass to the event of error, but just triggered in the internal code directly.

You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
Error: connect EHOSTUNREACH xx.xx.xx.xx:9092
    at Object.exports._errnoException (util.js:1018:11)
    at exports._exceptionWithHostPort (util.js:1041:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
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

1 participant