Closed ichxxx closed 3 years ago
Could you provide configuration and versions of the broker, proxy and python client lib ? I've just tried a python consumer using confluent-kafka 1.7.0 connecting to the brokers 2.8.0 via kafa-proxy using PLAIN transport and had no problems
I start kafka by docker, the version is 1.1.1
and my confluent-kafka version is 1.7.0
:
zookeeper:
image: wurstmeister/zookeeper
ports:
- "2181:2181"
kafka:
image: bitnami/kafka:1.1.1
depends_on: [ zookeeper ]
ports:
- "9092:9092"
environment:
- KAFKA_BROKER_ID=0
- KAFKA_CFG_ADVERTISED_LISTENERS=PLAINTEXT://10.101.104.8:9092
- KAFKA_CFG_LISTENERS=PLAINTEXT://0.0.0.0:9092
- KAFKA_CREATE_TOPICS="test:1:1"
- KAFKA_CFG_ZOOKEEPER_CONNECT=zookeeper:2181
- ALLOW_PLAINTEXT_LISTENER=yes
- KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE=true
I mapping ip 0.0.0.0
to a domain kafka.test.com
and change the configuration of kafka-proxy --bootstrap-server-mapping "10.101.104.8:9092,kafka.test.com:29092"
, and it works fine now.
Hi, I am trying to use kafka-proxy, but I got a problem: I can not consume message using python (both kafka-python and confluent-kafka-python are tried), and I didn't get any error message in kafka-proxy.
kafka-proxy
python code (python3.7)
kafka-proxy log
debug info in confluent-kafka-python (using kafka-proxy):
Keep send/receive FindCoordinatorRequest/Response repeatedly.
debug info in confluent-kafka-python (not using kafka-proxy):
It can successful connected. And I found when using kafka-proxy, the FindCoordinatorResponse is 5 bytes short.
Thanks fo any help!