Thanks Chris,
This is the way I gave defined Kafka brokers
docker run -d *--name kafka_broker0* -p *9092*:9092 -e
KAFKA_ADVERTISED_HOST_NAME=50.140.197.220 -e
ZOOKEEPER_IP=50.140.197.220 -e *KAFKA_BROKER_ID=0
*-e KAFKA_BROKER_PORT=9092 -e *KAFKA_ADVERTISED_PORT=9092* ches/kafka
docker run -d
Could it be that you changed the KAFKA_ADVERTISED_PORT and restarted those
brokers but didn't restart the rest (until now)?
I wouldn't be surprised if the other brokers continued to use the incorrect
advertised port.
On Mon, Jul 16, 2018 at 1:40 PM, Mich Talebzadeh
wrote:
> I restarted all Kafka
I restarted all Kafka dockers corresponding to broker 0-2 and now broker ID
0 is selected as leader and is working
${KAFKA_HOME}/bin/kafka-topics.sh --describe -zookeeper rhes75:2181
--topic final
Topic:final PartitionCount:3ReplicationFactor:3
Configs:
Topic: final
Also I noticed that bar broker ID =0, the connection to broker ID 1 )node
1) and broker ID 2 (node 2) could not be established
[2018-07-16 18:41:10,419] WARN [Producer clientId=console-producer]
Connection to node 1 could not be established. Broker may not be available.
(org.apache.kafka.clients.N
Thanks Chris,
I am afraid the issue is still there!
docker run -d --name kafka_broker0 -p 9092:9092 -e
KAFKA_ADVERTISED_HOST_NAME=50.140.197.220 -e ZOOKEEPER_IP=50.140.197.220 -e
KAFKA_BROKER_ID=0 -e KAFKA_BROKER_PORT=9092 -e *KAFKA_ADVERTISED_PORT=9092
*ches/kafka
${KAFKA_HOME}/bin/kafka-topi
I believe you need to use -e KAFKA_ADVERTISED_PORT=909..
On Mon, Jul 16, 2018 at 7:41 AM, Mich Talebzadeh
wrote:
> Hi,
>
> I have created a zookeeper and three brokers as dockers in a physical host
> as shown below
>
> [image: image.png]
>
> The followings are used to create Zookeeper and Kafka
Hi,
I have created a zookeeper and three brokers as dockers in a physical host
as shown below
[image: image.png]
The followings are used to create Zookeeper and Kafka dockers
docker run -d --name zookeeper -p 2181:2181 -p 2888:2888 -p 3888:3888
jplock/zookeeper
docker run -d --name kafka_broke
