[ 
https://issues.apache.org/jira/browse/KAFKA-18992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936228#comment-17936228
 ] 

José Armando García Sancio edited comment on KAFKA-18992 at 3/17/25 4:03 PM:
-----------------------------------------------------------------------------

[~frankvicky] The problem is that the "upgrade --release-version" assumes that 
the bootstrap mapping is also the upgrade mapping. At this point, the best 
solution is to make that the case by me implementing 
https://issues.apache.org/jira/browse/KAFKA-16538.

Otherwise, we are going to have to complicate the dependency mapping code in 
Features so that bootstrap versions are not the same as upgrade versions.

I think that we should assign this issue to me and let me fix it as part of 
https://issues.apache.org/jira/browse/KAFKA-16538 by making kraft.version 1 
upgradable.

I am going to assign the issue to me for now.


was (Author: jsancio):
[~frankvicky] The problem is that the "upgrade --release-version" assumes that 
the bootstrap mapping is also the upgrade mapping. At this point, the best 
solution is to make that the case by me implementing 
https://issues.apache.org/jira/browse/KAFKA-16538.

Otherwise, we are going to have to complicate the dependency mapping code in 
Features so that bootstrap versions are not the same as upgrade versions.

I think that we should assign this issue to me and let me fix it as part of 
KAFKA-16539 by making kraft.version 1 upgradable.

I am going to assign the issue to me for now.

> kafka-features.sh wronly output `upgraded kraft.version to 1`
> -------------------------------------------------------------
>
>                 Key: KAFKA-18992
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18992
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller, kraft
>    Affects Versions: 4.0.0
>            Reporter: Luke Chen
>            Assignee: José Armando García Sancio
>            Priority: Major
>             Fix For: 4.1.0
>
>
> When using static quorum and upgraded to v4.0, the upgrade command showed 
> `kraft.version was upgraded to 1.`, while the describe output is correctly 
> showed the FinalizedVersionLevel is 0.
>  
> {code:java}
> > bin/kafka-features.sh --bootstrap-server localhost:9094 upgrade 
> > --release-version 4.0
> group.version was upgraded to 1.
> kraft.version was upgraded to 1.
> metadata.version was upgraded to 25.
> transaction.version was upgraded to 2.
> > bin/kafka-features.sh --bootstrap-server localhost:9094 describe
> Feature: eligible.leader.replicas.version    SupportedMinVersion: 0    
> SupportedMaxVersion: 1    FinalizedVersionLevel: 0    Epoch: 3331
> Feature: group.version    SupportedMinVersion: 0    SupportedMaxVersion: 1    
> FinalizedVersionLevel: 1    Epoch: 3331
> Feature: kraft.version    SupportedMinVersion: 0    SupportedMaxVersion: 1    
> FinalizedVersionLevel: 0    Epoch: 3331
> Feature: metadata.version    SupportedMinVersion: 3.3-IV3    
> SupportedMaxVersion: 4.0-IV3    FinalizedVersionLevel: 4.0-IV3    Epoch: 3331
> Feature: transaction.version    SupportedMinVersion: 0    
> SupportedMaxVersion: 2    FinalizedVersionLevel: 2    Epoch: 3331 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to