.utils.KafkaScheduler)
org.apache.kafka.common.errors.ReplicaNotAvailableException: Replica with
id 32 is not available on broker 37
So, effectively a dead broker in ISR list makes at least the scheduled
isr-expiration operation non-working.
Unfortunately, I haven't been able to reproduce th
er (in this case broker 1) to remove
> > broker 0 from the ISR for this topic partition.
> >
> > Thanks
> > Avinash Bhat
> >
> > P.S: I am fairly new to Kafka; it will be great to get a confirmation on
> > the above from other folks.
> >
> > ----
onfirmation on
> the above from other folks.
>
> -Original Message-
> From: Ivan Yurchenko
> Sent: Thursday, February 13, 2020 5:27 PM
> To: users@kafka.apache.org
> Subject: Dead broker in ISR
>
> Hi Kafka community,
>
> We're running Kafka 2.4 and fac
ove from other folks.
-Original Message-
From: Ivan Yurchenko
Sent: Thursday, February 13, 2020 5:27 PM
To: users@kafka.apache.org
Subject: Dead broker in ISR
Hi Kafka community,
We're running Kafka 2.4 and facing a pretty strange situation.
Let's say there were three brokers in the
Hi Kafka community,
We're running Kafka 2.4 and facing a pretty strange situation.
Let's say there were three brokers in the cluster 0, 1, and 2. Then:
1. Broker 3 was added.
2. Partitions were reassigned from broker 0 to broker 3.
3. Broker 0 was shut down (not gracefully) and removed from
