[jira] [Created] (KAFKA-9256) mirrorMaker + kafka = java.lang.NoSuchMethodError: org.apache.kafka.common.requests.MetadataResponse.prepareResponse

["Rudik (Jira)" <ji...@apache.org>]

Rudik created KAFKA-9256:
----------------------------

             Summary: mirrorMaker + kafka = java.lang.NoSuchMethodError: org.apache.kafka.common.requests.MetadataResponse.prepareResponse
                 Key: KAFKA-9256
                 URL: https://issues.apache.org/jira/browse/KAFKA-9256
             Project: Kafka
          Issue Type: Bug
          Components: mirrormaker
    Affects Versions: 2.3.0
            Reporter: Rudik


kafkaBroker - 2.3.0

java - openjdk version "11.0.2" 2019-01-15

 

kafka cluster from = \{broker - os-4603:9092,os-4604:9092,os-4605:9092, auth - plain } \{zookeeper - os-4595:2181,os-4596:2181,os-4599:2181}

kafka cluster to = \{broker - os-4804:9092,os-4805:9092,os-4806:9092, auth - plain} \{zookeeper - os-4804:2181,os-4805:2181,os-4806:2181}

 

Start MirrorMaker:

[kafka@os-4804 kafka]$ bin/kafka-mirror-maker.sh --consumer.config ./config/mirrormaker_consumer_pdc.properties --num.streams 2 --producer.config ./config/mirrormaker_producer.pr operties --whitelist="connect-configs, connect-offsets, connect-status, last_topic"
WARNING: The default partition assignment strategy of the mirror maker will change from 'range' to 'roundrobin' in an upcoming release (so that better load balancing can be achiev ed). If you prefer to make this switch in advance of that release add the following to the corresponding config: 'partition.assignment.strategy=org.apache.kafka.clients.consumer.R oundRobinAssignor'
[2019-12-02 13:50:45,391] WARN The configuration 'zookeeper.connect' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)
[2019-12-02 13:50:45,483] WARN The configuration 'zookeeper.connect' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2019-12-02 13:50:45,508] WARN The configuration 'zookeeper.connect' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)
[2019-12-02 13:50:45,749] WARN [Consumer clientId=dp-MirrorMaker-group-0, groupId=dp-MirrorMaker-group] Connection to node -2 (os-4604/10.6.107.93:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2019-12-02 13:50:45,750] WARN [Consumer clientId=dp-MirrorMaker-group-1, groupId=dp-MirrorMaker-group] Connection to node -2 (os-4604/10.6.107.93:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2019-12-02 13:50:45,758] WARN [Consumer clientId=dp-MirrorMaker-group-0, groupId=dp-MirrorMaker-group] Connection to node -3 (os-4605/10.6.107.94:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)

 

logs in KafkaBroker:

[2019-12-02 13:51:54,020] ERROR [KafkaApi-1] Error when handling request: clientId=dp-MirrorMaker-group-1, correlationId=269, api=METADATA, body=\{topics=null,allow_auto_topic_crea tion=true,include_cluster_authorized_operations=false,include_topic_authorized_operations=false} (kafka.server.KafkaApis)
java.lang.NoSuchMethodError: org.apache.kafka.common.requests.MetadataResponse.prepareResponse(ILjava/util/List;Ljava/lang/String;ILjava/util/List;I)Lorg/apache/kafka/common/reque sts/MetadataResponse;
 at kafka.server.KafkaApis.$anonfun$handleTopicMetadataRequest$7(KafkaApis.scala:1103)
 at kafka.server.KafkaApis.$anonfun$handleTopicMetadataRequest$7$adapted(KafkaApis.scala:1096)
 at kafka.server.KafkaApis.sendResponseMaybeThrottle(KafkaApis.scala:2539)
 at kafka.server.KafkaApis.handleTopicMetadataRequest(KafkaApis.scala:1096)
 at kafka.server.KafkaApis.handle(KafkaApis.scala:116)
 at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:69)
 at java.base/java.lang.Thread.run(Thread.java:834)

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)