Blizzard / Blizzard/node-rdkafka

ERR__ALL_BROKERS_DOWN consumer never comes back up

Open
#960 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2.2k
Forks
403
PR merge metrics
No merged PRs in 30d

Description

**Environment Information**
- OS: Arch
- Node Version: 16.14.2
- NPM Version: 8.5.0
- C++ Toolchain: g++
- node-rdkafka version: 2.12.0

**Steps to Reproduce**

* Start your consumer
* Shut down your kafka instance
* Wait until you get all brokers down
* Start your kafka instance back
* You can't consume messages any more

**node-rdkafka Configuration Settings**

```
{
brokers: [...],
protocol: sasl,
sasl: {
mechanism: plain,
username: ...,
password: ...
},
group.id: ...,
event_cb: true
enable.auto.commit: true
}
```

**Additional context**

In my development and qa environment for the project I'm working on, I randomly receive ERR__ALL_BROKERS_DOWN after maybe a day or so of running. After this happens, the consumer never comes back up and no more messages are consumed.

Am I doing something wrong? Is there a way to recover from this event?

Using consumer-flow if that's relevant.

Also, it seems like [librdkafka v1.9.0](https://github.com/edenhill/librdkafka/blob/a913c75e1e09ef87232e9c7b044d8ab3ec404417/CHANGELOG.md) has a change that fixes false positives with all brokers down. Will there be a release of node-rdkafka that upgrades to v1.9.0 any time soon?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.