[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494731#comment-16494731
]
Don commented on KAFKA-3042:
----------------------------
We still observed "Cached zkVersion 54 not equal to that in zookeeper, skip
updating ISR" in our setup on confluent docker image 4.1.0 which includes kafka
1.1.0.
It was resulting in the broker disconnecting from the cluster. Restarting the
broker fixed the issue.
This happened at least twice a week.
Since we increased following timeouts to the values below, we haven't observed
the issue in several weeks:
- name: KAFKA_REPLICA_LAG_TIME_MAX_MS
value: "14000"
- name: KAFKA_ZOOKEEPER_SESSION_TIMEOUT_MS
value: "21000"
Unfortunately log retention was not setup when we were observing the issue.
> 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.0.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)
