Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Fri, 22 Feb 2013 17:26:13 +0000 (UTC)
From: "Guozhang Wang (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12632915.1361231555680.324294.1361553973210@arcas>
In-Reply-To: <JIRA.12632915.1361231555680@arcas>
References: <JIRA.12632915.1361231555680@arcas>
Subject: [jira] [Commented] (KAFKA-762) Improve second replica assignment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KAFKA-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584461#comment-13584461 ] 

Guozhang Wang commented on KAFKA-762:
-------------------------------------

I think that as long as the secondShift is different for two partition, even if their first replica is assigned to the same broker their following replicas would not be possibly assigned to the same broker?
                
> 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
>              Labels: p2
>             Fix For: 0.8
>
>         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