内外网访问 Kafka Listeners

listeners, advertised.listeners, 内外网分流........ 在云原生环境下，到底应该怎么配？通过动手实操了解

Spencer Ruport:

LISTENERS are what interfaces Kafka binds to. ADVERTISED_LISTENERS are how clients can connect.

注意图和下文颜色是对应的。

我们会用到一个很好用的小工具 [kcat](edenhill/kcat: Generic command line non-JVM Apache Kafka producer and consumer (github.com))。

跑一个 container, ENV 配置如下

key

value

ALLOW_PLAINTEXT_LISTENER

yes

KAFKA_CFG_LISTENERS

PLAINTEXT://:9092,CONTROLLER://:9093,EXTERNAL://:9094

KAFKA_CFG_ADVERTISED_LISTENERS

PLAINTEXT://kafka-bro-cn:9092,EXTERNAL://localhost:9094

KAFKA_CFG_LISTENER_SECURITY_PROTOCOL_MAP

CONTROLLER:PLAINTEXT,EXTERNAL:PLAINTEXT,PLAINTEXT:PLAINTEXT

container name 改名为 kafka-bro-cn (container name 的意思), 网络改名为 app-tier

1. 从宿主机访问

即在 host 上用 kcat

kcat 联系的是 listeners 中的一号监听器 EXTERNAL

kcat -b 127.0.0.1 -L
[root@ecs-6fd7 ~]# kcat -b 127.0.0.1:9094 -L
Metadata for all topics (from broker -1: 127.0.0.1:9094/bootstrap):
 1 brokers:
  broker 1 at localhost:9094 (controller)
 2 topics:
  topic "test" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
  topic "__consumer_offsets" with 50 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
    partition 1, leader 1, replicas: 1, isrs: 1
    partition 2, leader 1, replicas: 1, isrs: 1
    ......

注意看 broker 1 at localhost:9094 是 advertise.listener list 中的 Listener EXTERNAL 的内容。

2. 从同网络的其他容器访问

在 other containers on the same Docker network 用 kcat,

kcat 联系的是 listeners 中二号监听器 PLAINTEXT

docker run -it \
 --network=app-tier \
 edenhill/kcat:1.7.1 \
  -b kafka-bro-cn:9092 -L

结果如下

Metadata for all topics (from broker 1: kafka-bro-cn:9092/1):
 1 brokers:
  broker 1 at kafka-bro-cn:9092 (controller)
 2 topics:
  topic "test" with 1 partitions:
    partition 0, leader 1, replicas: 1, isrs: 1
    ......

注意看第2, 3行 1 brokers: broker 1 at kafka-bro-cn:9092 是 advertise.listener list 中的 Listener PLAINTEXT 的内容

3. 从同子网的其他宿主机访问

3 在 other host (同一子网subnet 中) 上用 kcat 怎么办呢？

访问该 host 内网ip

[root@ecs-6fd7-fb07 kcat]# kcat -b 172.31.0.16:9094 -L
Metadata for all topics (from broker -1: 172.31.0.16:9094/bootstrap):
 1 brokers:
  broker 1 at localhost:9094 (controller)
 0 topics:

(我重启了container 所以 topics 变 0了)

他给的 advertise.listener 是 list 中(确切说是 map )的二号 listener EXTERNAL, 内容是 localhost:9092

所以第一道关过了第二道可过不了

用 console-producer

[root@ecs-6fd7-fb07 kafka]bin/kafka-console-producer.sh --bootstrap-server 172.31.0.16:9094 --topic test1
>fist
[2023-06-29 18:13:19,104] WARN [Producer clientId=console-producer] Connection to node 1 (localhost/127.0.0.1:9094) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2023-06-29 18:13:19,204] WARN [Producer clientId=console-producer] Connection to node 1 (localhost/127.0.0.1:9094) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
......

改 broker 的 ENV ---- EXTERNAL://172.31.0.16:9094 好了

第一道：

[root@ecs-6fd7-fb07 bin]# kcat -b 172.31.0.16:9094 -L
Metadata for all topics (from broker 1: 172.31.0.16:9094/1):
 1 brokers:
  broker 1 at 172.31.0.16:9094 (controller)
 0 topics:

第二道：

[root@ecs-6fd7-fb07 bin]# ./kafka-console-producer.sh --bootstrap-server 172.31.0.16:9094 --topic test1
>this is first event
[2023-06-29 18:18:49,789] WARN [Producer clientId=console-producer] Error while fetching metadata with correlation id 4 : {test1=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
>this is second event
>this is thr^Hird event
>

虽然报了个 WARN 但其实写进去了:

[root@ecs-6fd7-fb07 kafka]# bin/kafka-console-consumer.sh --topic test1 --from-beginning --bootstrap-server 172.31.0.16:9094
this is first event
this is second event
this is third event

那么如果我想从外网访问呢？比如我的电脑 laptop

4. 公网访问

other host (从公网)

在 KAFKA_CFG_LISTENERS 添加一项 LAPTOP://:9095

在 KAFKA_CFG_ADVERTISED_LISTENERS 添加 LAPTOP://公网IP:9095

把 9095 映射出去 port: -'9095:9095' （想象一下路由器的路由表）

kafka-console-consumer.bat --topic test1 --from-beginning --bootstrap-server 公网IP:9095

PreviousKAFKA LISTENERS Next并发编程

Last updated 1 year ago