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

["M. Manna (Jira)" <ji...@apache.org>]

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

M. Manna commented on KAFKA-3042:
---------------------------------

We have been hit by this yesterday in Production and had an outage. I have added the same comments in the original ticket. We are running Kafka 2.4.1 with Confluent. This could've happened event with the most recent release versions too. I will change the priority to critical.

> 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: Critical
>              Labels: reliability
>         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
(v8.3.4#803005)