[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236180#comment-15236180
]
Robert Christ commented on KAFKA-3042:
--------------------------------------
The log on disk also stops and 00:39:46,246. It does not resume until
2016-04-09 01:00:54,529 in the next file.
The server log appears to continue right past this period until 00:59:15 which
is when I did the controlled shutdown
starting at 00:58:54 (that is an approximate time based on my typing date).
James noticed that the log ended at the same period as when our zkCli.sh
processes disconnected.
> 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
> 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)
