[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555485#comment-16555485
]
Don edited comment on KAFKA-3042 at 7/25/18 10:21 AM:
------------------------------------------------------
We tried reproducing the issue on confluent docker image 4.1.0 by commenting
out:
- #name: KAFKA_REPLICA_LAG_TIME_MAX_MS
#value: "14000"
- #name: KAFKA_ZOOKEEPER_SESSION_TIMEOUT_MS
#value: "21000"
In one of our environments.
Fortunately? we haven't observed "Cached zkVersion 54 not equal to that in
zookeeper, skip updating ISR" for almost two months.
It could be that we had a configuration issue, e.g. we used an older version of
kafka, when i reported "We still observed ...".
Sorry for the false alarm.
was (Author: donis):
We tried reproducing the issue on confluent docker image 4.1.0 by commenting
out:
#- name: KAFKA_REPLICA_LAG_TIME_MAX_MS
#value: "14000"
#- name: KAFKA_ZOOKEEPER_SESSION_TIMEOUT_MS
#value: "21000"
In one of our environments.
Fortunately? we haven't observed "Cached zkVersion 54 not equal to that in
zookeeper, skip updating ISR" for almost two months.
It could be that we had a configuration issue, e.g. we used an older version of
kafka, when i reported "We still observed ...".
Sorry for the false alarm.
> 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.1.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)
