[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158807#comment-15158807
]
Flavio Junqueira commented on KAFKA-3042:
-----------------------------------------
bq. 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.
But in this case, wouldn't the broker eventually recover? What I find
problematic here is that the descriptions and comments in the related jiras
mention the need of bouncing brokers, it shouldn't be necessary.
If anyone has state change logs to share for the period in which one of these
incidents occurred, it'd be nice to see them.
> 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
>
> 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)
