[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404314#comment-15404314
]
Jun Rao commented on KAFKA-3042:
--------------------------------
Thinking about this a bit more. An alternative approach is to extend
LeaderAndIsrRequest to include all endpoints for live_leaders. The follower can
then obtain the right host/port for the leader from
LeaderAndIsrRequest.live_leaders, instead of the metadata cache. This approach
is more general and won't be depending on the ordering of UpdateMetadataRequest
and LeaderAndIsrRequest. Since this is a protocol change, we will need to do a
KIP. With this change, LeaderAndIsrRequest and UpdateMetadataRequest will look
almost identical. The later still has an extra field for rack per broker. We
can look into combining the two requests in the future.
> 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)
