Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Connection stuck if first broker on the list is down
See original GitHub issueIssue:
let config = { brokers: ['broker1:9092', 'broker2:9092', 'broker3:9092'] }
assuming broker1:9092 is down, kafkajs will fail to connect to the cluster. But if the order
is :
let config = { brokers: ['broker2:9092', 'broker1:9092', 'broker3:9092'] }
or
let config = { brokers: ['broker3:9092', 'broker2:9092', 'broker1:9092'] }
The connection will work fine.
I’d expect kafkajs to be able to connect to the cluster in case one broker is down, and that broker is the first on the list, WDYT?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Update: it seems that it does manage to connect https://github.com/tulios/kafkajs/blob/master/src/broker/index.js#L79 but it get stuck on this call https://github.com/tulios/kafkajs/blob/master/src/broker/index.js#L82 which is related to the issue I currently have with this broker, so perhaps adding a timeout to this call will make the client more robust to this edge case
Fixed by #369