[jira] [Updated] (KAFKA-1215) Rack-Aware replica assignment option

["Joris Van Remoortere (JIRA)" <ji...@apache.org>]

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

Joris Van Remoortere updated KAFKA-1215:
----------------------------------------

    Attachment: rack_aware_replica_assignment_v2.patch

Rebased to trunk:
- Made rack-id optional, default to -1
- Carry max-replication through zookeeper in order to support add-partitions

Missing:
- There is currently no warning when changing a broker's rack-id
- There is no warning during manual replica (re)assignment if the assignment is not legal under the given max-rack-replication factor

> Rack-Aware replica assignment option
> ------------------------------------
>
>                 Key: KAFKA-1215
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1215
>             Project: Kafka
>          Issue Type: Improvement
>          Components: replication
>    Affects Versions: 0.8.0, 0.8.1
>            Reporter: Joris Van Remoortere
>            Assignee: Neha Narkhede
>             Fix For: 0.8.0, 0.8.1
>
>         Attachments: rack_aware_replica_assignment_v1.patch, rack_aware_replica_assignment_v2.patch
>
>
> Adding a rack-id to kafka config. This rack-id can be used during replica assignment by using the max-rack-replication argument in the admin scripts (create topic, etc.). By default the original replication assignment algorithm is used because max-rack-replication defaults to -1. max-rack-replication > -1 is not honored if you are doing manual replica assignment (preffered).
> If this looks good I can add some test cases specific to the rack-aware assignment.
> I can also port this to trunk. We are currently running 0.8.0 in production and need this, so i wrote the patch against that.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)