[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239575#comment-15239575
]
Jun Rao edited comment on KAFKA-3042 at 4/13/16 4:45 PM:
---------------------------------------------------------
[~ijuma]], we fixed a few issues related to soft failure post 0.8.2. However,
there could be other issues that we don't know yet.
[~delbaeth], [~wushujames], even when we fix all the bugs related to soft
failure, it would still be good to avoid it in the first place since it only
adds overhead. A 60000 zookeeper.session.timeout seems high though. Do you know
what's causing the ZK session timeout? Is it related to GC or network?
was (Author: junrao):
[~ismael juma], we fixed a few issues related to soft failure post 0.8.2.
However, there could be other issues that we don't know yet.
[~delbaeth], [~wushujames], even when we fix all the bugs related to soft
failure, it would still be good to avoid it in the first place since it only
adds overhead. A 60000 zookeeper.session.timeout seems high though. Do you know
what's causing the ZK session timeout? Is it related to GC or network?
> updateIsr should stop after failed several times due to zkVersion issue
> -----------------------------------------------------------------------
>
> Key: KAFKA-3042
> URL: https://issues.apache.org/jira/browse/KAFKA-3042
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2.1
> Environment: jdk 1.7
> centos 6.4
> Reporter: Jiahongchao
> Fix For: 0.10.0.0
>
> Attachments: controller.log, server.log.2016-03-23-01,
> state-change.log
>
>
> sometimes one broker may repeatly log
> "Cached zkVersion 54 not equal to that in zookeeper, skip updating ISR"
> I think this is because the broker consider itself as the leader in fact it's
> a follower.
> So after several failed tries, it need to find out who is the leader
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
