Thanks you clarificaiton.
On Thu, 26 Sep 2019 at 00:07, Harper Henn
wrote:
> Hi,
>
> I think this is accomplished with metadata requests. A client sends this
> request (along with a list of topics it's interested in) to a broker in the
> cluster and gets back a list of leader/replica partitions.
Hi,
I think this is accomplished with metadata requests. A client sends this
request (along with a list of topics it's interested in) to a broker in the
cluster and gets back a list of leader/replica partitions. This is cached
and refreshed, and when a client receives the "Not a Leader" error (mea
Hi,
Can anyone clarify the procedure of a client getting to know about a Kafka
leader failover and identify the new leader?
Thanks.