You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2014/04/21 16:52:16 UTC
[jira] [Commented] (KAFKA-1407) Broker can not return to ISR
because of BadVersionException
[ https://issues.apache.org/jira/browse/KAFKA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975605#comment-13975605 ]
Jun Rao commented on KAFKA-1407:
--------------------------------
When this happens, do you see any connection loss to ZK?
> Broker can not return to ISR because of BadVersionException
> -----------------------------------------------------------
>
> Key: KAFKA-1407
> URL: https://issues.apache.org/jira/browse/KAFKA-1407
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Affects Versions: 0.8.1
> Reporter: Dmitry Bugaychenko
> Assignee: Neha Narkhede
>
> Each morning we found a broker out of ISR at stuck with log full of messages:
> {code}
> INFO | jvm 1 | 2014/04/21 08:36:21 | [2014-04-21 09:36:21,907] ERROR Conditional update of path /brokers/topics/topic2/partitions/1/state with data {"controller_epoch":46,"leader":2,"version":1,"leader_epoch":38,"isr":[2]} and expected version 53 failed due to org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = BadVersion for /brokers/topics/topic2/partitions/1/state (kafka.utils.ZkUtils$)
> INFO | jvm 1 | 2014/04/21 08:36:21 | [2014-04-21 09:36:21,907] INFO Partition [topic2,1] on broker 2: Cached zkVersion [53] not equal to that in zookeeper, skip updating ISR (kafka.cluster.Partition)
> {code}
> It seems that it can not recover after short netwrok break down and the only way to return it is restart it using kill -9.
--
This message was sent by Atlassian JIRA
(v6.2#6252)