[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525938#comment-15525938
]
Andreas Schroeder edited comment on KAFKA-3042 at 9/27/16 12:22 PM:
--------------------------------------------------------------------
Since this issue wasn't updated for over a month, a short note that I ran into
this issue as well: I tested with a local, 3-node Docker-based cluster (version
0.10.0.1) when I repeatedly hunted down the controller broker and restarted
him. Since I'm not yet that deep into Kafka and the codebase, I can only report
from a user perspective the consequences I saw:
* The failure to shrink the ISR affected partitions of all topics, including
__consumer_offsets.
* Two brokers ran repeatedly into this issue within 20 minutes.
* During that time, producers were unable to write data to the cluster
* Also during that time, I saw messages being lost even though I used a
replication factor of 3, min insync replicas of 2 and acks=all.
was (Author: andreas-schroeder):
Since this issue wasn't updated for over a month, a short note that I ran into
this issue as well: I tested with a local, 3-node Docker-based cluster when I
repeatedly hunted down the controller broker and restarted him. Since I'm not
yet that deep into Kafka and the codebase, I can only report from a user
perspective the consequences I saw:
* The failure to shrink the ISR affected partitions of all topics, including
__consumer_offsets.
* Two brokers ran repeatedly into this issue within 20 minutes.
* During that time, producers were unable to write data to the cluster
* Also during that time, I saw messages being lost even though I used a
replication factor of 3, min insync replicas of 2 and acks=all.
> 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
> Fix For: 0.10.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
(v6.3.4#6332)
