Running this seems to indicate that there is a leader at 0:
$ ./bin/kafka-topics.sh --zookeeper MY.EXTERNAL.IP:2181 --describe
--topic test123
--> Topic:test123 PartitionCount:1 ReplicationFactor:1 Configs:
Topic: test123 Partition: 0 Leader: 0 Replicas: 0 Isr: 0
I reran this test and my server.log indicates that there is a leader at 0:
...
[2015-06-16 21:58:04,498] INFO 0 successfully elected as leader
(kafka.server.ZookeeperLeaderElector)
[2015-06-16 21:58:04,642] INFO Registered broker 0 at path
/brokers/ids/0 with address MY.EXTERNAL.IP:9092. (kafka.utils.ZkUtils$)
[2015-06-16 21:58:04,670] INFO [Kafka Server 0], started
(kafka.server.KafkaServer)
[2015-06-16 21:58:04,736] INFO New leader is 0
(kafka.server.ZookeeperLeaderElector$LeaderChangeListener)
I see this error in the logs when I send a message from the producer:
[2015-06-16 22:18:24,584] ERROR [KafkaApi-0] error when handling request
Name: TopicMetadataRequest; Version: 0; CorrelationId: 7; ClientId:
console-producer; Topics: test123 (kafka.server.KafkaApis)
kafka.admin.AdminOperationException: replication factor: 1 larger than
available brokers: 0
at
kafka.admin.AdminUtils$.assignReplicasToBrokers(AdminUtils.scala:70)
If it sees my broker when I start it up, why can't it find it later when it
receives a message?
Thanks,
-Mike
On Tue, Jun 16, 2015 at 3:11 PM, Gwen Shapira <gshap...@cloudera.com> wrote:
> The topic warning is a bug (i.e the fact that you get a warning on
> perfectly valid parameter). We fixed it for next release.
>
> It is also unrelated to the real issue with the LeaderNotAvailable
>
>
