Hello,
I've begun migrating some of my Zookeeper Kafka clusters to KRaft. A
behaviour I've noticed twice across two different kafka cluster
environments is after provisioning a kraft controller quorum in migration
mode, it is possible for a kafka broker to become an active controller
alongside a k
elete the /controller znode (as
> the procedure describe). Only in this case a broker is able to "win" the
> /controller by using -1 as epoch (because the /controller znode doesn't
> exist anymore).
> Not sure if in your case you made some mistakes during the migration or
>
Hi there,
I recently ran into an issue where I noticed that we had many old broker
and configs set in zookeeper that were migrated over in KRaft
mode.
For example, this was a cluster default from 2020 that was moved over:
get /config/brokers/
{"version":1,"config":{"num.network.threads":"6","num
