[jira] [Comment Edited] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

["Pengwei (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817467#comment-15817467 ] 

Pengwei edited comment on KAFKA-3042 at 1/11/17 7:27 AM:
---------------------------------------------------------

[~lindong]  It seems I still encounter this issue after apply your patch in our test enviroment
The log is also logging the message "Cached zkVersion ...." and cannot recover

The reproducer step we used is to stop three broker's network some time and restart the network, then we found one of the brokers keep printing the cached zkversion log


was (Author: pengwei):
[~lindong]  It seems I still encounter this issue after apply your patch in our test enviroment
The log is also logging the message "Cached zkVersion ...." and cannot recover

> 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
>            Assignee: Dong Lin
>              Labels: reliability
>             Fix For: 0.10.2.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)