hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (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 Tue, 28 Oct 2014 04:16:34 GMT

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

Vinayakumar B commented on HDFS-6995:

Yes Chris. Missed the commit. I will merge to branch-2.6 soon.

> Block should be placed in the client's 'rack-local' node if 'client-local' node is not
> ------------------------------------------------------------------------------------------------
>                 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

View raw message