WARN Error while fetching metadata with correlation id 0 : {testtopic=LEADER_NOT_AVAILABLE}

centos6.5+kafka2.11

配置好的Kafka创建生产者时出现下面的错误

root@ubuntu-130:kafka/bin# ./kafka-console-producer.sh --broker-list 192.168.0.14:9092 --topic testtopic
>hello
[2019-07-14 23:42:47,318] WARN Error while fetching metadata with correlation id 1 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:47,512] WARN Error while fetching metadata with correlation id 3 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:47,631] WARN Error while fetching metadata with correlation id 4 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:47,790] WARN Error while fetching metadata with correlation id 5 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:48,228] WARN Error while fetching metadata with correlation id 6 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:48,365] WARN Error while fetching metadata with correlation id 7 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:48,496] WARN Error while fetching metadata with correlation id 8 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:48,635] WARN Error while fetching metadata with correlation id 9 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:48,777] WARN Error while fetching metadata with correlation id 10 : {testtopic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-07-14 23:42:48,916] WARN Error while fetching metadata with correlation id 11 : {testtopic=LEADER_NOT

testtopic=LEADER_NOT_AVAILABLE没有主节点可用，
解决方案

1. 更改broker.id的值

在server.properties文件中

2. 重新启动kafka

./kafka-server-start.sh config/server.properties

创建topic和生产者，看是否正常运行，如果不可以,换回原来的broker.id再重新启动一下就好了。

看了网上很多资料，发现很多删除日志信息的，就是修改了broker.id之后把log目录下的所有信息都删除再重新启动就可以了，如果上面的方法不行可以尝试一下！