Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 4 Sep 2014 21:23:24 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12737306.1409203650000.635.1409865804566@Atlassian.JIRA>
In-Reply-To: <JIRA.12737306.1409203650000@Atlassian.JIRA>
References: <JIRA.12737306.1409203650000@Atlassian.JIRA>
 <JIRA.12737306.1409203650620@arcas>
Subject: [jira] [Resolved] (HDFS-6961) Archival Storage:
 BlockPlacementPolicy#chooseTarget should check each valid storage type in
 each choosing round
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jing Zhao resolved HDFS-6961.
-----------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed

I've committed this.

> Archival Storage: BlockPlacementPolicy#chooseTarget should check each valid storage type in each choosing round
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-6961
>                 URL: https://issues.apache.org/jira/browse/HDFS-6961
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: balancer, namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-6961.000.patch, HDFS-6961.001.patch, HDFS-6961.002.patch, HDFS-6961.002.patch, HDFS-6961.003.patch
>
>
> Currently in each choosing round of BlockPlacementPolicy#chooseTarget (e.g., round 1 for choosing local storage, round 2 for remote rack, etc.), we only take into account the first storage type in the storage type list. This may 
> fail to choose the local machine or sometimes may even fail to choose enough nodes.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)