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

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

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

Kemal ERDEN commented on KAFKA-3042:
------------------------------------

We've hit this on 2.1.0 - I actually raised a new Jira KAFKA-7888 which has merged logs of the brokers attached and some more detail. Restarting the broker which logs the zkVersion issue repeatedly seems to fix the issue but in the meantime we have lost expired messages.

> 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
>          Components: controller
>    Affects Versions: 0.10.0.0
>         Environment: jdk 1.7
> centos 6.4
>            Reporter: Jiahongchao
>            Assignee: Dong Lin
>            Priority: Major
>              Labels: reliability
>             Fix For: 2.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
(v7.6.3#76005)