[
https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-5329:
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.11.0.1)
0.11.0.0
Status: Resolved (was: Patch Available)
Issue resolved by pull request 3257
[https://github.com/apache/kafka/pull/3257]
> Replica list in the metadata cache on the broker may have different order
> from zookeeper
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-5329
> URL: https://issues.apache.org/jira/browse/KAFKA-5329
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.2.1
> Reporter: Jiangjie Qin
> Assignee: Ismael Juma
> Labels: newbie
> Fix For: 0.11.0.0
>
>
> It looks that in {{PartitionStateInfo}} we are storing the replicas in a set
> instead of a Seq. This causes the replica order to be lost. In most case it
> is fine, but in the context of preferred leader election, the replica order
> determines which replica is the preferred leader of a partition. It would be
> useful to make the order always be consistent with the order in zookeeper.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
