[ https://issues.apache.org/jira/browse/KAFKA-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030981#comment-14030981 ]
Joris Van Remoortere commented on KAFKA-1215: --------------------------------------------- [~jjkoshy] I am out till the end of the month. I was going to take a deeper look at how to integrate this into the auto-rebalance as that has since been released (post initial patch). > 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.8.2 > > 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.2#6252)