To answer my own question for people who may run into this same issue
in the future: it appears that this behavior is by design, or at least
parts of Kafka are written to work around this issue.
Looking at the class kafka.javaapi.consumer.ConsumerRebalanceListener,
it can be seen that the method b
Hi,
I've run into an issue using the old high-level consumer, and I'd like
to verify that it is indeed a bug (I'm pretty sure it is), or see if
I'm just doing something wrong.
The situation is that I have two consumers (A and B) in the same
consumer group reading from a single topic. One consumer
