Hi all, we were testing kafka disaster/recover in our Sites.
Anyway do avoid the scenario in this post ?
https://blog.softwaremill.com/help-kafka-ate-my-data-ae2e5d3e6576
But, the Unclean Leader exception is not an option in our case.
FYI..
We needed to deactivated our systemctl for kafka broke
Thats a disaster recovery simulation, we need to validate a way to avoid
that in a disaster case/scenario!! I mean If I have a disaster and the
servers got rebooted we need to prevent its kafka weaknes.
Regards,
Jhanssen Fávaro de Oliveira
On Thu, Jun 17, 2021 at 6:30 PM Sunil Unnithan wrote
Why not use min.isr=2 in this case?
>
> On Thu, Jun 17, 2021 at 5:11 PM Jhanssen Fávaro
> wrote:
>
> > Basically, if we have 3 brokers and the ISR == all, and in the case that a
> > leader partition broker was the last server that was restarted/rebooted,
> >
Basically, if we have 3 brokers and the ISR == all, and in the case that a
leader partition broker was the last server that was restarted/rebooted, and
during its startup got a disk corruption, all the followers will mark the topic
as offline.
So, If the last broker leader that got the corrupte
Hi all, we were testing kafka disaster/recover in our Sites.
Anyway do avoid the scenario in this post ?
https://blog.softwaremill.com/help-kafka-ate-my-data-ae2e5d3e6576
But, the Unclean Leader exception is not an option in our case.
FYI..
We needed to deactivated our systemctl for kafka broke
ocol as it is described in the
> documentation, I got the CPU increase when I upgraded the 1st instance as
> the first step.
>
> Cheers,
> Peter
>
> On Fri, 26 Feb 2021 at 18:35, Jhanssen Fávaro
> wrote:
>
> > Hi Peter,
> > I am on the same, a lot of questio
Hi Peter,
I am on the same, a lot of questions about the Kafka's upgrade process. But
looks like tha this CPU Increase is expected, at least while you don't
finish every broker upgrade.
In this case, when you say you didn't change the version, you say that for
any brokers right ?
Basically, you s
