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] [Updated] (HDFS-6995) Block should be placed in the client's 'rack-local' node if 'client-local' node is not available
Date Mon, 06 Oct 2014 09:07:34 GMT

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

Vinayakumar B updated HDFS-6995:
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

committed to trunk and branch-2.

Thanks [~umamaheswararao] and [~hitliuyi] for the reviews

> 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