Hi Behrang, All reads and writes of a partition go through the leader of that partition. If the leader of a partition is down you will not be able to produce/consume data in it until a new leader is elected. Typically it happens in a few seconds, after that you should be able to use that partition again. If your problem persists I recommend figuring out why leader election does not happen. You might be able to work with other partitions, at least those that have leaders on brokers that are up.
Cheers, Sandor Murakozi On Tue, Feb 20, 2018 at 9:00 AM, Behrang <behran...@gmail.com> wrote: > Hi, > > I have a Kafka cluster with 3 nodes. > > I pass the nodes in the cluster to a consumer app I am building as > bootstrap servers. > > When one of the nodes in the cluster is down, the consumer group sometimes > CAN read records from the server but sometimes CAN NOT. > > In both cases, the same Kafka node is down. > > Is this behavior normal? Isn't it enough to only have one of the nodes in > the Kafka cluster be up and running? I have not delved much into setup and > administration of Kafka clusters, but I thought Kafka uses the nodes for HA > and as long as one node is up and running, the cluster remains healthy and > working. > > Best regards, > Behrang Saeedzadeh >
