[
https://issues.apache.org/jira/browse/KAFKA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-762:
--------------------------
Attachment: kafka-762_v1.patch
Attach patch v1. It addresses the problem by starting the second replica from a
random interval after the first replica.
> Improve second replica assignment
> ---------------------------------
>
> Key: KAFKA-762
> URL: https://issues.apache.org/jira/browse/KAFKA-762
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Jun Rao
> Priority: Blocker
> Attachments: kafka-762_v1.patch
>
>
> Currently, for partitions from different topics, if the first replica is
> assigned to the same broker, their second replica is also assigned to the
> same broker. This means that when a broker fails, many leaders on the failed
> broker will be moved to the same broker, and thus introduces more load on
> that broker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
