[
https://issues.apache.org/jira/browse/AMBARI-20015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated AMBARI-20015:
----------------------------------------
Description:
On a Kerberoized cluster when we restart Kafka, some times Kafka start fails
with below error
[2016-02-29 08:44:15,339] FATAL [Kafka Server 1001], Fatal error during
KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
java.lang.RuntimeException: A broker is already registered on the path
/brokers/ids/1001. 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.
at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:295)
at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:281)
at kafka.server.KafkaHealthcheck.register(KafkaHealthcheck.scala:64)
at kafka.server.KafkaHealthcheck.startup(KafkaHealthcheck.scala:45)
at kafka.server.KafkaServer.startup(KafkaServer.scala:231)
at
kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:37)
at kafka.Kafka$.main(Kafka.scala:67)
at kafka.Kafka.main(Kafka.scala)
[2016-02-29 08:44:15,343] INFO [Kafka Server 1001], shutting down
(kafka.server.KafkaServer)
was:
On a Kerberoized cluster when we restart Kafka, Kafka start fails with below
error
[2016-02-29 08:44:15,339] FATAL [Kafka Server 1001], Fatal error during
KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
java.lang.RuntimeException: A broker is already registered on the path
/brokers/ids/1001. 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.
at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:295)
at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:281)
at kafka.server.KafkaHealthcheck.register(KafkaHealthcheck.scala:64)
at kafka.server.KafkaHealthcheck.startup(KafkaHealthcheck.scala:45)
at kafka.server.KafkaServer.startup(KafkaServer.scala:231)
at
kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:37)
at kafka.Kafka$.main(Kafka.scala:67)
at kafka.Kafka.main(Kafka.scala)
[2016-02-29 08:44:15,343] INFO [Kafka Server 1001], shutting down
(kafka.server.KafkaServer)
> Kafka restart on a Kerberoized cluster fails (happens some times)
> -----------------------------------------------------------------
>
> Key: AMBARI-20015
> URL: https://issues.apache.org/jira/browse/AMBARI-20015
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
>
> On a Kerberoized cluster when we restart Kafka, some times Kafka start fails
> with below error
> [2016-02-29 08:44:15,339] FATAL [Kafka Server 1001], Fatal error during
> KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
> java.lang.RuntimeException: A broker is already registered on the path
> /brokers/ids/1001. 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.
> at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:295)
> at kafka.utils.ZkUtils.registerBrokerInZk(ZkUtils.scala:281)
> at kafka.server.KafkaHealthcheck.register(KafkaHealthcheck.scala:64)
> at kafka.server.KafkaHealthcheck.startup(KafkaHealthcheck.scala:45)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:231)
> at
> kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:37)
> at kafka.Kafka$.main(Kafka.scala:67)
> at kafka.Kafka.main(Kafka.scala)
> [2016-02-29 08:44:15,343] INFO [Kafka Server 1001], shutting down
> (kafka.server.KafkaServer)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
