[
https://issues.apache.org/jira/browse/KAFKA-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17934595#comment-17934595
]
José Armando García Sancio commented on KAFKA-16538:
----------------------------------------------------
[~zheguang] Kafka 3.9.0 support dynamically changing your controller cluster if
the new cluster is created using 3.9.0. What 3.9.0 doesn't support is upgrading
an existing cluster to 3.9.0 and have it support dynamically changing your
controller cluster.
If a user needs dynamically changing the controller cluster (KIP-853) to
migrate from ZK to KRaft, the recommendation is to first upgrade the ZK Kafka
cluster to 3.9.0. Deploy a new Kafka controller cluster that supports dynamic
membership and finally perform the ZK to KRaft migration.
Hope that helps.
> Support UpdateFeatures for kraft.version so we can go from static quorums to
> dynamic
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-16538
> URL: https://issues.apache.org/jira/browse/KAFKA-16538
> Project: Kafka
> Issue Type: Sub-task
> Reporter: José Armando García Sancio
> Assignee: José Armando García Sancio
> Priority: Major
>
> Should:
> # Route request to cluster metadata kraft client.
> # KRaft leader should check the supported version of all voters and observers
> ## voter information comes from VoterSet
> ## observer information is push down to kraft by the metadata controller
> # Persist both the kraft.version and voter set in one control batch
> We need to allow for the kraft.version to succeed while the metadata
> controller changes may fail. This is needed because there will be two batches
> for this updates. One control record batch which includes kraft.version and
> voter set, and one metadata batch which includes the feature records.
>
> This change should also improve the handling of UpdateVoter to allow the
> request when the kraft.version is 0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
