hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2547) Design doc is wrong about default block placement policy.
Date Fri, 11 Nov 2011 12:10:52 GMT

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

Harsh J commented on HDFS-2547:
-------------------------------

Aaron,

{{BlockPlacementPolicyDefault}} has proper comments in it, on trunk. It was 0.20's ReplicationTargetChooser
that threw me off there. Reopening to fix against 0.20.
                
> Design doc is wrong about default block placement policy.
> ---------------------------------------------------------
>
>                 Key: HDFS-2547
>                 URL: https://issues.apache.org/jira/browse/HDFS-2547
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.20.1
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Trivial
>             Fix For: 0.24.0
>
>         Attachments: HDFS-2547.patch
>
>
> bq. For the common case, when the replication factor is three, HDFS's placement policy
is to put one replica on one node in the local rack, another on a node in a different (remote)
rack, and the last on a different node in the same *remote* rack.
> Should actually be: "and the last on a different node in the same *local* rack."

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message