Hi Paolo,
The best way to do this would be to have broker3 start up with the same
broker id as the failed broker2. broker3 will then rejoin the cluster,
begin catching up with broker1, and eventually rejoin the ISR. If it starts
up with a new broker id, you'll need to run the partition reassignmen
Hello,
in order to try running Kafka in Kubernetes I'm facing the following problem ...
Imagine that I start a cluster with a zookeeper instance and two kafka broker.
I create a topic with one partition but replication factor 2 : I have broker1
as leader and broker2 as follower.
All works great
