You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2019. It is now read-only.
We saw an example of this in our latest Travis build on my Docker PR (here), and I've also encountered this in my dev environment. We should track down what the problem is and fix it if possible.
Current workaround is to run docker-compose up again until the Kafka container doesn't die.
The text was updated successfully, but these errors were encountered:
[2016-02-18 18:56:18,519] FATAL Fatal error during KafkaServerStartable startup. Prepare to shutdown (kafka.server.KafkaServerStartable)
java.lang.RuntimeException: A broker is already registered on the path /brokers/ids/1. This probably indicates that you either have configured a brokerid that is already in use, or else you have shutdown this broker and restarted it faster than the zookeeper timeout so it appears to be re-registering.
so @sirsean's inclination that this was a Zookeeper issue sounds about right to me.
I also see an instance of this error related to non-graceful shutdown that a PR exists for upstream on the container image that we're using, but that doesn't seem to describe the clean creation case: wurstmeister/kafka-docker#58
We saw an example of this in our latest Travis build on my Docker PR (here), and I've also encountered this in my dev environment. We should track down what the problem is and fix it if possible.
Current workaround is to run
docker-compose up
again until the Kafka container doesn't die.The text was updated successfully, but these errors were encountered: