kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiangjie Qin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper
Date Fri, 26 May 2017 05:15:04 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jiangjie Qin updated KAFKA-5329:
--------------------------------
    Summary: Replica list in the metadata cache on the broker may have different order from
zookeeper  (was: Metadata cache on the broker may have replica list may have different order
from zookeeper)

> 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
>              Labels: newbie
>             Fix For: 0.11.0.1
>
>
> 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)

Mime
View raw message