[
https://issues.apache.org/jira/browse/KAFKA-20117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056229#comment-18056229
]
Chia-Ping Tsai commented on KAFKA-20117:
----------------------------------------
[~davidarthur] is this a blocker? 3.9.2 is already in RC
BTW, are you working on it? If you are tied up, we're happy to take over
> Improve ClusterControlManager error message
> -------------------------------------------
>
> Key: KAFKA-20117
> URL: https://issues.apache.org/jira/browse/KAFKA-20117
> Project: Kafka
> Issue Type: Improvement
> Reporter: David Arthur
> Priority: Minor
> Fix For: 3.9.2, 4.3.0, 4.0.2, 4.1.2
>
>
> During the ZK to KRaft migration, if the broker and controller are not on the
> same IBP/MetadataVersion, we will get registration errors on the controller
> like:
> {code:java}
> [ERROR] 2025-11-24 06:20:42,779 [quorum-controller-9992-event-handler]
> org.apache.kafka.controller.ClusterControlManager
> throwUnsupportedVersionDueToIncompatibleFeature -
> [ControllerServer id=9992] Unable to register broker 2 because it does not
> support finalized version 14
> of confluent.metadata.version. The broker wants a version between 11 and 11,
> inclusive.
> {code}
>
> This can be a bit confusing for operators since they do not normally deal
> with the feature level numbers, but rather the IBP strings (e.g., "3.6-IV2").
> We should enhance this error message to include the corresponding release
> string for the feature levels.
> Since this impacts migration, I've marked the fix version for 3.9.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
