Hi,
In addition to the above suggestion, I think you can also check the broker
logs clearly. You should see the reason. For example, here's what I saw in
my logs:
[2021-02-26 16:38:45,777] INFO [GroupCoordinator 0]: Member
consumer-groupId-1-7e24136f-8d7e-4303-a150-32dae06c18c0 in group groupId
ha
There might be many causes, but from broker's point of view: This consumer
is dead.
Consumers are considered dead when one of the following happended:
1. didn't send out heartbeat for session.timeout.ms(defaults to 10
seconds) period of time. (Consumers sent heart beat ever
heartbeat.interval.ms)
Kafka clients need to be able to differentiate the different brokers, and
have explicit control which broker to connect to.
Why? Each partition resides in a specific broker, and the client needs to
connect to the partition leader to perform read & writes, if they are all
under the same virtual ip,
Honestly I didnt get this question.
Please elaborate.
On Sun, 4 Jul 2021 at 5:34 PM, M. Manna wrote:
> Hello,
>
> Is it currently possible to use a single endpoint for advertised.listeners,
> which is in front of all my brokers? the flow for example
>
> broker1-->| V
> broker2--
Hello,
Is it currently possible to use a single endpoint for advertised.listeners,
which is in front of all my brokers? the flow for example
broker1-->| V
broker2-->| I
broker3-->| P
I was under the impression that I can reach any broker I wanted (assuming
that broker is
Hi,
There is something called as heartbet consumer thread.
This threads running on consumer keeps sending heartbeats at regular
interval as per the setting heartbeat.interval.ms. It keeps on telling
broker that I am very much alive.
https://docs.confluent.io/platform/current/installation/configura
Dear kafka Experts
Could one of you please help to explain what this below log in broker
instance mean..and what scenarios it would occur when there is no change
done .
INFO [GroupCoordinator 9610]: Member
webhooks-retry-app-840d3107-833f-4908-90bc-ea8c394c07c3-StreamThread-2-consumer-f87c3b85-5
