[
https://issues.apache.org/jira/browse/KAFKA-21426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Khyati V reassigned KAFKA-21426:
--------------------------------
Assignee: Khyati V
> kafka-features.sh upgrade --release-version upgrades kraft.version and
> converts static quorums to dynamic
> ---------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-21426
> URL: https://issues.apache.org/jira/browse/KAFKA-21426
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Reporter: Mickael Maison
> Assignee: Khyati V
> Priority: Major
>
> During an upgrade, after installing the new binaries, we instruct to run the
> "bin/kafka-features.sh upgrade --release-version <version>" command. [0]
> This command upgrades all features including kraft.version. It means clusters
> still using a static quorum get upgraded to dynamic quorum automatically and
> irreversibly.
> This is unexpected and dangerous as it changes several operation procedures
> such as adding nodes and changing disks. Also all nodes still have the static
> configurations controller.quorum.voters, instead of what is expected in
> dynamic mode.
> Upgrading with the release-version flag should ignore kraft.version if that
> is currently 0.
> A workaround in the meantime is to explicitly set the feature versions. First
> retrieve the default feature versions for the new Kafka version using:
> bin/kafka-features.sh version-mapping --release-version <version>
> Then set them using (intentionally skipping kraft.version):
> bin/kafka-features.sh --bootstrap-server localhost:9092 upgrade \
> --feature metadata.version=<> \
> --feature transaction.version=<> \
> --feature group.version=<> \
> --feature eligible.leader.replicas.version=<> \
> --feature share.version=<> \
> --feature streams.version=<>
> 0: https://kafka.apache.org/44/getting-started/upgrade/#upgrading-to-430
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)