Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 4 Sep 2014 09:42:51 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12739087.1409823509000.16869.1409823771819@Atlassian.JIRA>
In-Reply-To: <JIRA.12739087.1409823509000@Atlassian.JIRA>
References: <JIRA.12739087.1409823509000@Atlassian.JIRA>
 <JIRA.12739087.1409823509850@arcas>
Subject: [jira] [Updated] (HDFS-6995) Block should be placed in the client's
 'rack-local' node if 'client-local' node is not available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinayakumar B updated HDFS-6995:
--------------------------------
    Affects Version/s: 2.5.0
               Status: Patch Available  (was: Open)

> Block should be placed in the client's 'rack-local' node if 'client-local' node is not available
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-6995
>                 URL: https://issues.apache.org/jira/browse/HDFS-6995
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.5.0
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-6995-001.patch
>
>
> HDFS cluster is rack aware.
> Client is in different node than of datanode,
> but Same rack contains one or more datanodes.
> In this case first preference should be given to select 'rack-local' node.
> Currently, since no Node in clusterMap corresponds to client's location, blockplacement policy choosing a *random* node as local node and proceeding for further placements.


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