[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159676#comment-15159676
]
James Cheng commented on KAFKA-3042:
------------------------------------
[~fpj], I have controller.log, state-change.log, and server.log for a broker
that is experiencing this. When gzipped, the files are 100mb (in total for all
3), (almost 1gig when uncompresssed)
Is that too big to attach to JIRA? I can try slicing them smaller. I would need
guidance on what parts are most important to you. In server.log, I see 'Cached
zkVersion [45] not equal to that in zookeeper, skip updating ISR
(kafka.cluster.Partition)' showing up as a specific time in the logs. I can
send you the slices of all 3 logs around that timeframe.
> 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)
