[
https://issues.apache.org/jira/browse/KAFKA-8716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Yang updated KAFKA-8716:
---------------------------
Description:
We are trying to upgrade kafka binary from 2.1 to 2.2.1 or 2.3.0. For both
versions, the broker with updated binary (2.2.1 or 2.3.0) could not get started
due to zookeeper session expiration exception. This error happens repeatedly
and the broker could not start because of this.
Below is our zk related setting in server.properties:
{code}
zookeeper.connection.timeout.ms=6000
zookeeper.session.timeout.ms=6000
{code}
The following is the stack trace, and we are using zookeeper 3.5.3. Instead of
waiting for a few seconds, the SESSIONEXPIRED error returned immediately in
CheckedEphemeral.create call. Any insights?
[2019-07-25 18:07:35,712] INFO Creating /brokers/ids/80 (is it secure? false)
(kafka.zk.KafkaZkClient)
[2019-07-25 18:07:35,724] ERROR Error while creating ephemeral at
/brokers/ids/80 with return code: SESSIONEXPIRED
(kafka.zk.KafkaZkClient$CheckedEphemeral)
[2019-07-25 18:07:35,731] ERROR [KafkaServer id=80] Fatal error during
KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode =
Session expired
at org.apache.zookeeper.KeeperException.create(KeeperException.java:130)
at kafka.zk.KafkaZkClient$CheckedEphemeral.create(KafkaZkClient.scala:1725)
at kafka.zk.KafkaZkClient.checkedEphemeralCreate(KafkaZkClient.scala:1689)
at kafka.zk.KafkaZkClient.registerBroker(KafkaZkClient.scala:97)
at kafka.server.KafkaServer.startup(KafkaServer.scala:260)
at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
at kafka.Kafka$.main(Kafka.scala:75)
at kafka.Kafka.main(Kafka.scala)
was:
We are trying to upgrade kafka binary from 2.1 to 2.2.1 or 2.3.0. For both
versions, the broker with updated binary (2.2.1 or 2.3.0) could not get started
due to zookeeper session expiration exception.
Below is our zk related setting in server.properties:
{code}
zookeeper.connection.timeout.ms=6000
zookeeper.session.timeout.ms=6000
{code}
The following is the stack trace, and we are using zookeeper 3.5.3. Instead of
waiting for a few seconds, the SESSIONEXPIRED error returned immediately in
CheckedEphemeral.create call. Any insights?
[2019-07-25 18:07:35,712] INFO Creating /brokers/ids/80 (is it secure? false)
(kafka.zk.KafkaZkClient)
[2019-07-25 18:07:35,724] ERROR Error while creating ephemeral at
/brokers/ids/80 with return code: SESSIONEXPIRED
(kafka.zk.KafkaZkClient$CheckedEphemeral)
[2019-07-25 18:07:35,731] ERROR [KafkaServer id=80] Fatal error during
KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode =
Session expired
at org.apache.zookeeper.KeeperException.create(KeeperException.java:130)
at kafka.zk.KafkaZkClient$CheckedEphemeral.create(KafkaZkClient.scala:1725)
at kafka.zk.KafkaZkClient.checkedEphemeralCreate(KafkaZkClient.scala:1689)
at kafka.zk.KafkaZkClient.registerBroker(KafkaZkClient.scala:97)
at kafka.server.KafkaServer.startup(KafkaServer.scala:260)
at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
at kafka.Kafka$.main(Kafka.scala:75)
at kafka.Kafka.main(Kafka.scala)
> broker cannot join the cluster after upgrading kafka binary from 2.1.1 to
> 2.2.1 or 2.3.0
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-8716
> URL: https://issues.apache.org/jira/browse/KAFKA-8716
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Yu Yang
> Priority: Critical
>
> We are trying to upgrade kafka binary from 2.1 to 2.2.1 or 2.3.0. For both
> versions, the broker with updated binary (2.2.1 or 2.3.0) could not get
> started due to zookeeper session expiration exception. This error happens
> repeatedly and the broker could not start because of this.
> Below is our zk related setting in server.properties:
> {code}
> zookeeper.connection.timeout.ms=6000
> zookeeper.session.timeout.ms=6000
> {code}
> The following is the stack trace, and we are using zookeeper 3.5.3. Instead
> of waiting for a few seconds, the SESSIONEXPIRED error returned immediately
> in CheckedEphemeral.create call. Any insights?
> [2019-07-25 18:07:35,712] INFO Creating /brokers/ids/80 (is it secure? false)
> (kafka.zk.KafkaZkClient)
> [2019-07-25 18:07:35,724] ERROR Error while creating ephemeral at
> /brokers/ids/80 with return code: SESSIONEXPIRED
> (kafka.zk.KafkaZkClient$CheckedEphemeral)
> [2019-07-25 18:07:35,731] ERROR [KafkaServer id=80] Fatal error during
> KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
> org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode
> = Session expired
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:130)
> at kafka.zk.KafkaZkClient$CheckedEphemeral.create(KafkaZkClient.scala:1725)
> at kafka.zk.KafkaZkClient.checkedEphemeralCreate(KafkaZkClient.scala:1689)
> at kafka.zk.KafkaZkClient.registerBroker(KafkaZkClient.scala:97)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:260)
> at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
> at kafka.Kafka$.main(Kafka.scala:75)
> at kafka.Kafka.main(Kafka.scala)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
