[
https://issues.apache.org/jira/browse/KAFKA-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372058#comment-14372058
]
Allen Wang commented on KAFKA-1215:
-----------------------------------
What's the status of this JIRA?
I have two questions:
- Can we simply use string for rack ID? This will make it much easier to use in
AWS where the zone ID is a string. Otherwise there will be unnecessary code to
convert them back and forth.
- Why is max-rack-replication necessary? In most use cases you want to have
even distribution of replicas to racks without having to consider max
replication per rack.
> 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
> Reporter: Joris Van Remoortere
> Assignee: Jun Rao
> Fix For: 0.9.0
>
> 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.3.4#6332)
