You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2016/02/10 20:17:18 UTC

[jira] [Updated] (KAFKA-3226) Replicas collections should use List instead of Set in order to maintain order

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

Grant Henke updated KAFKA-3226:
-------------------------------
    Status: Patch Available  (was: Open)

> Replicas collections should use List instead of Set in order to maintain order
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-3226
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3226
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.9.0.0
>            Reporter: Grant Henke
>            Assignee: Grant Henke
>             Fix For: 0.9.0.1
>
>
> Found an issue where LeaderAndIsrRequest and UpdateMetadataRequest store the replicas in a Set. This potentially changes the order of the replicas list, which is important because the first replica is the "preferred" replica. 
> The question is, do these requests need to go through a deprecation/compatibility cycle, or are they considered internal messages?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)