[
https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248498#comment-15248498
]
Onur Karaman commented on KAFKA-3042:
-------------------------------------
It looks like LeaderAndIsrRequest structure is identical to
UpdateMetadataRequest. Joel pointed me to KAFKA-901 for some background on this.
I feel like kafka's wire protocol would be simpler if the controller just sends
out UpdateMetadataRequests to the rest of the cluster and we get rid of the
concept of LeaderAndIsrRequest. Upon receiving UpdateMetadataRequest from a
controller, a broker updates its caches and potentially does the work
associated with becoming a leader or follower. Am I oversimplifying the
situation?
> 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.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
(v6.3.4#6332)
