Thanks a lot folks, this is really helpful.
> I believe the limitation that this documentation is hinting at is the
> motivation for KIP-996
I'll make sure to check out KIP-996 and the references linked there.
Thanks for the summary as well, I really appreciate it.
Cheers,
Dani
On Tue, Feb
A 5-node quorum doesn't make a lot of sense in a setting where those nodes
are also Kafka brokers. When they're ZooKeeper voters, a quorum* of 5
makes a lot of sense, because you can take an unscheduled voter failure
during a rolling-reboot scheduled maintenance without significant service
Hi Dani,
I believe the limitation that this documentation is hinting at is the
motivation for KIP-996 [1], and the notice in the documentation would
be removed once KIP-996 lands.
You can read the KIP for a brief explanation and link to a more
in-depth explanation of the failure scenario.
While
Hello,
I would like to clarify a statement I found in the KRaft documentation, in
the deployment section [1]:
> More than 3 controllers is not recommended in critical environments. In
the rare case of a partial network failure it is possible for the cluster
metadata quorum to become unavailable.
