kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Stein (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KAFKA-1217) Rack-Aware replica assignment option
Date Thu, 23 Jan 2014 17:40:38 GMT

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

Joe Stein reassigned KAFKA-1217:
--------------------------------

    Assignee: Joe Stein  (was: Neha Narkhede)

> Rack-Aware replica assignment option
> ------------------------------------
>
>                 Key: KAFKA-1217
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1217
>             Project: Kafka
>          Issue Type: Improvement
>          Components: replication
>    Affects Versions: 0.8.0, 0.8.1
>            Reporter: Joris Van Remoortere
>            Assignee: Joe Stein
>             Fix For: 0.8.0, 0.8.1
>
>
> 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)

Mime
View raw message