Thanks. This is a good example to trigger rebalance. We may set
max.poll.records to a small number and set max.poll.interval.ms to a large
number to avoid this situation. In some cases the heartbeat simply cannot reach
Kakfa (maybe because of network problem), which can also trigger rebalance. I
thank you, Ismael!
a follow up question (or two :) ):
-- our clients (consumers and producers) are all upgraded to Kafka 2.4.0 / ZK
3.5.6 version at this time, and since it is a very involved process to upgrade
them, I'd want to leave them at that for now. Any issues you can think of
running cli
Answers inline.
On Fri, Aug 14, 2020 at 6:46 AM Marina Popova
wrote:
> thank you, Ismael!
> a follow up question (or two :) ):
> -- our clients (consumers and producers) are all upgraded to Kafka 2.4.0 /
> ZK 3.5.6 version at this time, and since it is a very involved process to
> upgrade them,
Congrats John! Well deserved!
-Matthias
On 8/11/20 2:14 PM, John Roesler wrote:
> Thanks for your kind words, all. This is truly an honor.
> -John
>
> On Mon, 2020-08-10 at 16:26 -0700, Boyang Chen wrote:
>> Congrats Mr. John!
>>
>>
>> On Mon, Aug 10, 2020 at 3:02 PM Adam Bellemare
>> wrote:
>>