[
https://issues.apache.org/jira/browse/KAFKA-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927877#comment-17927877
]
Guang Zhao edited comment on KAFKA-16538 at 2/17/25 10:38 PM:
--------------------------------------------------------------
Thanks for clarifying, [~jsancio].
So, we're eager to see this fix in before 4.0.0 is based on our assumption that
(1) 3.9 is the last version supporting Zookeeper and its migration to KRaft,
and (2) Zookeeper to static KRaft quorum, then to dynamic quorum is the
migration path to go, if we want to avoid ending up with new controllers
permanently.
Please correct me if I'm wrong!
was (Author: JIRAUSER308070):
Thanks for clarifying, [~jsancio]! So, we're eager to see this fix in before
4.0.0 is based on our assumption that (1) 3.9 is the last version supporting
Zookeeper and its migration to KRaft, and (2) Zookeeper to static KRaft quorum,
then to dynamic quorum is the migration path to go, if we want to avoid ending
up with new controllers permanently. Please correct me if I'm wrong!
> 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)
