Kafka.common.KafkaException:fetching topic Metadata for topics

2016-10-26 11:05:29,716  warn [flume_ dx2.zdp.ol-1477451127056-e2015d55-leader-finder-thread] kafka.consumer.consumerfetchermanager$ leaderfinderthread  (line 89)  [flume_dx2.zdp.ol-1477451127056-e2015d55-leader-finder-thread],  failed to find leader for set ([v4-avail-service-request,0]) Kafka.common.kafkaexception: fetching topic metadata for topics [set ( V4-avail-service-request)] from broker [arraybuffer (brokerendpoint (0, ip-192-168-110-4.cn-north-1.compute.internal,9092))] failedat kafka.client.clientutils$. Fetchtopicmetadata (clientutils.scala:72) at kafka.client.clientutils$.fetchtopicmetadata (ClientUtils.scala : At kafka.consumer.consumerfetchermanager$leaderfinderthread.dowork (consumerfetchermanager.scala:66) at  kafka.utils.shutdownablethread.run (shutdownablethread.scala:63) caused by:  Java.nio.channels.closedchannelexceptionat kafka.neTwork. Blockingchannel.send (blockingchannel.scala:110) at kafka.producer.syncproducer.liftedtree1$1 ( syncproducer.scala:76) at kafka.producer.syncproducer.kafka$producer$syncproducer$ $doSend ( syncproducer.scala:75) at kafka.producer.syncproducer.send (syncproducer.scala:120) at  Kafka.client.clientutils$.fetchtopicmetadata (clientutils.scala:58) ...  3 more

Flume subscription data from Kafka error failed to find leader for Set

Flume deployed locally, Kafka clusters are deployed on the AWS Cloud.

Solutions

Consume-side server configuration/etc/hosts file, where the machine name from the Kafka service-side private DNS name is the same (this name can be seen in the error message)

123.123.123.123 ip-192-168-110-4.cn-north-1.compute.internal

This article is from the "Chocolate Black" blog, be sure to keep this source http://10120275.blog.51cto.com/10110275/1865792

Kafka.common.KafkaException:fetching topic Metadata for topics