hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6995) Block should be placed in the client's 'rack-local' node if 'client-local' node is not available
Date Sat, 18 Oct 2014 13:59:36 GMT

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

Hudson commented on HDFS-6995:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #1905 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1905/])
HDFS-6995. Block should be placed in the client's 'rack-local' node if 'client-local' node
is not available (vinayakumarb) (vinayakumarb: rev cba1f9e3896c0526fa748cd1bb13470d5fae584a)
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestDefaultBlockPlacementPolicy.java


> 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
>             Fix For: 2.6.0
>
>         Attachments: HDFS-6995-001.patch, HDFS-6995-002.patch, HDFS-6995-003.patch, HDFS-6995-004.patch,
HDFS-6995-005.patch, HDFS-6995-006.patch, HDFS-6995-007.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)

Mime
View raw message