Kafka Kerberos认证报WARN Error while fetching metadata with correlation id 1 : {las=LEADER_NOT_AVAILABLE}

服务器没有域名，本来只有一个网口，IP是10.43.190.104，配置Kerberos认证时，创建principal为kafka/10.43.190.104@HADOOP.COM启动认证没问题，可以正常生产消费消息。

后来服务器加了一个万兆网口，IP是10.0.1.1创建principal为kafka/10.0.1.1@HADOOP.COM，生产消息报错。

环境

kafka kafka_2.11-0.11.0.1

相关配置

krb5.conf

# Configuration snippets may be placed in this directory as well
includedir /etc/krb5.conf.d/

[logging]
 default = FILE:/var/log/krb5libs.log
 kdc = FILE:/var/log/krb5kdc.log
 admin_server = FILE:/var/log/kadmind.log

[libdefaults]
 default_realm = HADOOP.COM
 dns_lookup_realm = false
 dns_lookup_kdc = 10.0.1.1:88
 ticket_lifetime = 500d
 renew_lifetime = 500d
 forwardable = true

[realms]
 HADOOP.COM = {
  kdc = 10.0.1.1:88
  admin_server = 10.0.1.1:749
  default_domain = HADOOP.COM
 }

[domain_realm]
 .hadoop.com = HADOOP.COM
 hadoop.com = HADOOP.COM

server.properties

advertised.listeners=SASL_PLAINTEXT://10.0.1.1:9092
listeners=SASL_PLAINTEXT://10.0.1.1:9092
security.inter.broker.protocol=SASL_PLAINTEXT
sasl.mechanism.inter.broker.protocol=GSSAPI
sasl.enabled.mechanisms=GSSAPI
sasl.kerberos.service.name=kafka

producer.properties，增加如下配置

security.protocol = SASL_PLAINTEXT
sasl.mechanism = GSSAPI
sasl.kerberos.service.name =kafka

consumer.properties，增加如下配置

security.protocol = SASL_PLAINTEXT
sasl.mechanism = GSSAPI
sasl.kerberos.service.name =kafka

kafka-run-class.sh

if [ -z "$KAFKA_JVM_PERFORMANCE_OPTS" ]; then
  KAFKA_JVM_PERFORMANCE_OPTS="-server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+DisableExplicitGC -Djava.awt.headless=true -Djava.security.krb5.conf=/etc/krb5.conf -Djava.security.auth.login.config=/home/install/kafka_2.11-0.11.0.1//config/kafka-jaas.conf"
fi

报错信息

采用命令行生产数据

bin/kafka-console-producer.sh --broker-list 10.0.1.1:9092 --topic las --producer.config config/producer.properties

报错信息

WARN Error while fetching metadata with correlation id 1 : {las=LEADER_NOT_AVAILABLE}
WARN Error while fetching metadata with correlation id 2 : {las=LEADER_NOT_AVAILABLE}
WARN Error while fetching metadata with correlation id 3 : {las=LEADER_NOT_AVAILABLE}