The Kafka Broker is running.
The topology worker log showed an error:
" 2015-12-07 14:58:49 s.k.ZkCoordinator [INFO] Task [1/1] Refreshing partition
manager connections
2015-12-07 14:58:49 s.k.DynamicBrokersReader [ERROR] Node /brokers/ids/0 does
not exist
2015-12-07 14:58:49 s.k.DynamicBrokersReader [INFO] Read partition info from
zookeeper: GlobalPartitionInformation{partitionMap={}}
2015-12-07 14:58:49 s.k.KafkaUtils [WARN] there are more tasks than partitions
(tasks: 1; partitions: 0), some tasks will be idle
2015-12-07 14:58:49 s.k.KafkaUtils [WARN] Task [1/1] no partitions assigned
2015-12-07 14:58:49 s.k.ZkCoordinator [INFO] Task [1/1] Deleted partition
managers: []
2015-12-07 14:58:49 s.k.ZkCoordinator [INFO] Task [1/1] New partition managers:
[]
2015-12-07 14:58:49 s.k.ZkCoordinator [INFO] Task [1/1] Finished refreshing "
Regards,
Daniel
-----Original Message-----
From: Zhang, Edward (GDI Hadoop) [mailto:[email protected]]
Sent: Monday, December 07, 2015 2:51 PM
To: [email protected]
Subject: Re: cannot produce messages with Kafka after reboot
The error message looks say kafka server(broker) is not up. Can you double
check if kafka server is running?
Thanks
Edward
On 12/7/15, 14:30, "Daniel Zhou"
<[email protected]<mailto:[email protected]>> wrote:
>Hi all,
>
>I met a problem: after I reboot my machines, Kafka service cannot
>produce messages.
>When I tried to send out the messages with producer, error occurs:
>"bin/kafka-console-producer.sh --broker-list centos.da2:6667 --topic
>test1 Message
>
>WARN Error while fetching metadata [{TopicMetadata for topic test1 ->
>No partition metadata for topic test1 due to
>kafka.common.LeaderNotAvailableException}] for topic [test1]: class
>kafka.common.LeaderNotAvailableException
>(kafka.producer.BrokerPartitionInfo)"
>
>Before that, everything works fine, has anyone met this problem before?
>
>
>Regards,
>Daniel
