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

Rameshkanna N commented on KAFKA-18938:
---------------------------------------

Hi [~yangpoan] , while starting the {*}controllers{*}, it shows {*}metadata 
version 3.0-IV1{*}, but when formatting the storage, it shows {*}3.9-IV1{*}. I 
can't add controllers dynamically, and I am getting the following exception:
Can you please help me with this?
WARN [AdminClient clientId=adminclient-1] The remote node is not a CONTROLLER 
that supports the KIP-919 DESCRIBE_CLUSTER api. 
(org.apache.kafka.clients.admin.internals.AdminMetadataManager)
org.apache.kafka.common.errors.UnsupportedVersionException: 
Direct-to-controller communication is not supported with the current 
MetadataVersion.
org.apache.kafka.common.errors.UnsupportedVersionException: 
Direct-to-controller communication is not supported with the current 
MetadataVersion.
java.util.concurrent.ExecutionException: 
org.apache.kafka.common.errors.UnsupportedVersionException: 
Direct-to-controller communication is not supported with the current 
MetadataVersion.
    at 
java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
    at 
java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2005)
    at 
org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
    at 
org.apache.kafka.tools.MetadataQuorumCommand.handleAddController(MetadataQuorumCommand.java:431)
    at 
org.apache.kafka.tools.MetadataQuorumCommand.execute(MetadataQuorumCommand.java:147)
    at 
org.apache.kafka.tools.MetadataQuorumCommand.mainNoExit(MetadataQuorumCommand.java:81)
    at 
org.apache.kafka.tools.MetadataQuorumCommand.main(MetadataQuorumCommand.java:76)
Caused by: org.apache.kafka.common.errors.UnsupportedVersionException: 
Direct-to-controller communication is not supported with the current 
MetadataVersion.

> Kraft version and metadata version wrongly showing
> --------------------------------------------------
>
>                 Key: KAFKA-18938
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18938
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller, kraft
>    Affects Versions: 3.9.0
>            Reporter: Rameshkanna N
>            Priority: Major
>
> I am using Kafka {*}3.9.0{*}. When starting a {*}KRaft controller{*}, it 
> shows {*}metadata version 3.0-IV1{*}, but when formatting storage, it shows 
> {*}version 3.9-IV0{*}. When I try to confirm the version using:
> {{sh kafka-features.sh --bootstrap-controller localhost:9091 describe}}
> it shows {*}finalized KRaft version 0{*}.
> Can anyone help me resolve this issue?
> Logs:
> sh kafka-features.sh --bootstrap-controller localhost:9091 describe
> Feature: kraft.version    SupportedMinVersion: 0    SupportedMaxVersion: 1    
> FinalizedVersionLevel: 0    Epoch: 6
> Feature: metadata.version    SupportedMinVersion: 3.0-IV1    
> SupportedMaxVersion: 3.9-IV0  
>  FinalizedVersionLevel: 3.9-IV0    Epoch: 6
> Server.log:
> [2025-03-06 13:40:40,569] INFO [ControllerServer id=102] Waiting for all of 
> the SocketServer Acceptors to be started (kafka.server.ControllerServer)
> [2025-03-06 13:40:40,569] INFO [ControllerServer id=102] Finished waiting for 
> all of the SocketServer Acceptors to be started 
> (kafka.server.ControllerServer)
> [2025-03-06 13:40:40,569] INFO [ControllerRegistrationManager id=102 
> incarnation=h-3EozNTQZGbhcsV_119Fg] initialized channel manager. 
> (kafka.server.ControllerRegistrationManager)
> [2025-03-06 13:40:40,569] INFO [ControllerRegistrationManager id=102 
> incarnation=h-3EozNTQZGbhcsV_119Fg] maybeSendControllerRegistration: cannot 
> register yet because the metadata.version is still 3.0-IV1, which does not 
> support KIP-919 controller registration.



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

Reply via email to