You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am opening this issue just for the sake of asking a question. When the KafkaJS library performs a heartbeat call to the Kafka cluster, and receives an error that the consumer group is being rebalanced:
will KafkaJS pause the consuming for that consumer? (and presumably resume it when this consumer successfully rejoins the group) - this would make sense as it is no longer clear for which topic partitions the consumer is responsible
will KafkaJS start preparing the consumer to issue a ReJoin request to Kafka?
The reasons behind these questions of mine are the following two:
We are seeing evidence of both 1. and 2. happening in the case of the Java consumer;
If we manually implement 1. and 2. to happen during our application-level handling of heartbeat it seems we can solve some nasty issues of constantly seeing rebalancing.
Thanks a lot for your time,
Krum.
The text was updated successfully, but these errors were encountered:
Hi Team,
I am opening this issue just for the sake of asking a question. When the KafkaJS library performs a
heartbeat
call to the Kafka cluster, and receives an error that the consumer group is being rebalanced:Looking at https://github.com/tulios/kafkajs/blob/master/src/consumer/runner.js#L207-L216 it seems that neither of these two happen.
The reasons behind these questions of mine are the following two:
heartbeat
it seems we can solve some nasty issues of constantly seeing rebalancing.Thanks a lot for your time,
Krum.
The text was updated successfully, but these errors were encountered: