[ https://issues.apache.org/jira/browse/KAFKA-9444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rishabh Bohra updated KAFKA-9444: --------------------------------- External issue URL: https://stackoverflow.com/questions/59592518/kafka-broker-doesnt-find-cluster-id-and-creates-new-one-after-docker-restart > Cannot connect to zookeeper after updating the kafka config > ----------------------------------------------------------- > > Key: KAFKA-9444 > URL: https://issues.apache.org/jira/browse/KAFKA-9444 > Project: Kafka > Issue Type: Bug > Affects Versions: 2.4.0 > Reporter: Rishabh Bohra > Priority: Major > Labels: mesosphere > > h4. *Issue:* > While connecting the kafka with zookeeper at a custom path, in the broker-0, > this error message pops up- > {{ERROR Fatal error during KafkaServer startup. Prepare to shutdown > (kafka.server.KafkaServer) kafka.common.InconsistentClusterIdException: The > Cluster ID 2yEEELdtRfKOJQiEurdoFg doesn't match stored clusterId > Some(H8dPCWwzRCK4eDmH3l5vvA) in meta.properties. The broker is trying to join > the wrong cluster. Configured zookeeper.connect may be wrong. at > kafka.server.KafkaServer.startup(KafkaServer.scala:220) at > kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:44) at > kafka.Kafka$.main(Kafka.scala:84) at kafka.Kafka.main(Kafka.scala)}} > *Steps:* > {{1. Start the kafka cluster without any zookeeper path/url}} > {{2. Update the kafka configuration with the provided path for zookeeper.}} > {{3. Check broker logs}} > *Package Version:* > Zookeeper: 3.4.14 > Zookeeper Client - Zookeeper-3.4.14.jar > Kafka - 2.12-2.4.0 > Similar issue can be found > [here|https://stackoverflow.com/questions/59592518/kafka-broker-doesnt-find-cluster-id-and-creates-new-one-after-docker-restart] -- This message was sent by Atlassian Jira (v8.3.4#803005)