Yes, you're right. No need to seek the offsets in onPartitionsAssigned
method internally KafkaConsumer handles it.
Thanks for sharing this with me. I'll update it.
--Kamal
On Mon, Apr 18, 2016 at 7:29 PM, Florian Hussonnois
wrote:
> Yes, but the
Yes, but the ConsumerRebalanceListener is optional and by the default
KafkaConsumer uses a NoOpConsumerRebalanceListener if no one is provided.
I think the seek() is already done internally when a consumer joins or
quits the group. I'm not sure this line is actually needed.
2016-04-18 15:31
When a new consumer joins to the group, it should start to read data
from where the other consumer left.
--Kamal
On Mon, Apr 18, 2016 at 6:58 PM, Florian Hussonnois
wrote:
> Thank you very much, the example is really helpful.
>
> My last question is : Why is it necessay
Thank you very much, the example is really helpful.
My last question is : Why is it necessay to seek the consumer offsets into
the onPartitionsAssigned method ?
Hi Florian,
This may be helpful
https://github.com/omkreddy/kafka-examples/blob/master/consumer/src/main/java/kafka/examples/consumer/advanced/AdvancedConsumer.java
--Kamal
On Fri, Apr 15, 2016 at 2:57 AM, Jason Gustafson wrote:
> Hi Florian,
>
> It's actually OK if
Hi Florian,
It's actually OK if processing takes longer than the heartbeat interval,
but it does need to finish before the session timeout expires or the
consumer will be kicked out of the group (which typically is revealed by
commit failures). If the problem is just that the consumer is handling
Hi everyone,
I have a use case where a message can take longer than '
heartbeat.interval.ms' to be processed by my application. As I understand
the heartbeats of consumer are done while the poll method is invoked.
I would like to instantiate a worker thread to process the messages but I
need to