unable to open connection to broker - kafka

最新推荐文章于 2024-02-20 13:32:03 发布

Blue summer

最新推荐文章于 2024-02-20 13:32:03 发布

阅读量836

点赞数

分类专栏： Kafka 文章标签： kafka listeners kowl

本文链接：https://blog.csdn.net/u010039418/article/details/128488726

版权

Kafka 专栏收录该内容

4 篇文章 0 订阅

订阅专栏

问题

在准备使用kowl来作为kafka管理面板时，发现一直无法连接到broker，提示机器hostname无法解析。

[root@node1 ~]# docker run -p 8080:8080 -e KAFKA_BROKERS=192.168.0.181:9092 quay.io/cloudhut/kowl:master
{"level":"info","msg":"config filepath is not set, proceeding with options set from env variables and flags"}
{"level":"info","ts":"2022-12-29T14:07:48.817Z","msg":"started Kowl","version":"master","git_sha":"59f68da86afe0e3c02ee1d0a1d3f372c6598ade1","built":"2022-05-16T15:03:02Z"}
{"level":"info","ts":"2022-12-29T14:07:48.819Z","msg":"connecting to Kafka seed brokers, trying to fetch cluster metadata"}
{"level":"warn","ts":"2022-12-29T14:07:48.923Z","msg":"unable to open connection to broker","source":"kafka_client","addr":"node1:9092","broker":"0","err":"dial tcp: lookup node1 on 192.168.0.1:53: no such host"}

分析

先确认zk和kafka服务状态，并且尝试创建topic和消费消息，确认服务确实是正常的，因此怀疑是配置问题。因为node1是我的本地hostname，在网关上肯定是无法解析的，那为什么会使用这个hostname来作为目标地址去解析呢。google了下，是因为默认的server.properties有如下配置，

# The address the socket server listens on. It will get the value returned from
# java.net.InetAddress.getCanonicalHostName() if not configured.
#   FORMAT:
#     listeners = listener_name://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
# listeners=PLAINTEXT://:9092

因此，当我们没有配置listeners时，就会用java.net.InetAddress.getCanonicalHostName()获取到的hostname来解析目标地址，这样对于我们的环境肯定是有问题的，因此修改配置如下，

listeners=PLAINTEXT://192.168.0.181:9092

然后重启kafka服务，此时再连接，就不会报错，

[root@node1 ~]# docker run -p 8080:8080 -e KAFKA_BROKERS=192.168.0.181:9092 quay.io/cloudhut/kowl:master
{"level":"info","msg":"config filepath is not set, proceeding with options set from env variables and flags"}
{"level":"info","ts":"2022-12-29T14:16:05.459Z","msg":"started Kowl","version":"master","git_sha":"59f68da86afe0e3c02ee1d0a1d3f372c6598ade1","built":"2022-05-16T15:03:02Z"}
{"level":"info","ts":"2022-12-29T14:16:05.460Z","msg":"connecting to Kafka seed brokers, trying to fetch cluster metadata"}
{"level":"info","ts":"2022-12-29T14:16:05.607Z","msg":"successfully connected to kafka cluster","advertised_broker_count":1,"topic_count":0,"controller_id":0,"kafka_version":"v3.1"}
{"level":"info","ts":"2022-12-29T14:16:05.611Z","msg":"creating Kafka connect HTTP clients and testing connectivity to all clusters"}
{"level":"info","ts":"2022-12-29T14:16:05.611Z","msg":"tested Kafka connect cluster connectivity","successful_clusters":0,"failed_clusters":0}
{"level":"info","ts":"2022-12-29T14:16:05.611Z","msg":"successfully create Kafka connect service"}
{"level":"info","ts":"2022-12-29T14:16:05.784Z","msg":"Server listening on address","address":"[::]:8080","port":8080}