Open kolotyluk opened 7 years ago
I have the same problem on my local machine 👍
I notice you added placement constraints when you transitioned to using stack deploy...And that they seem reversed (i.e. zookeeper on a worker node, all kafka instances on manager nodes). Do you just have one manager node in your docker cluster? Is it a relatively small EC2 instance? If you've overloaded that one Docker host with all of your kafka brokers, it's possible that they're all running slow enough that they don't always respond to interbroker requests before they time out, which Kafka would flag as a connection problem.
I have a similar issue, I posted this question on question on Stack Overflow.
I am able to run a stable cluster using docker-compose with
This works find on my developer system. However, when I try to get an equivalent cluster running on AWS, the cluster never becomes stable. I am using
docker stack . . .
withThis stack comes up, but what happens is:
WARN Connection to node xxxx could not be established. Broker may not be available.
WARN Connection to node xxxx could not be established. Broker may not be available.
docker-compose
.Any help would be greatly appreciated.