[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237839#comment-15237839
]
Robert Christ commented on KAFKA-3042:
--------------------------------------
We turned on unclean leader election due to encountering KAFKA-3410. We really
want
to turn it back off but we need to get a bit of stability before we do. We can
live with the data
loss for the moment.
We are experimenting with minimum ISR and how it behaves in various failure
cases.
We expect to increase it for all of our replicated topics. We overlooked it
when we were starting
out and now we are trying to catch up.
> 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)
