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

Todd Lipcon commented on HDFS-2825:
-----------------------------------

Allen - I agree it would be useful to set on the writer side. But that's not 
quite the original patch, which operates DFS-wide.
                
> Add test hook to turn off the writer preferring its local DN
> ------------------------------------------------------------
>
>                 Key: HDFS-2825
>                 URL: https://issues.apache.org/jira/browse/HDFS-2825
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.24.0, 0.23.1
>
>         Attachments: hdfs-2825.txt, hdfs-2825.txt
>
>
> Currently, the default block placement policy always places the first replica 
> in the pipeline on the local node if there is a valid DN running there. In 
> some network designs, within-rack bandwidth is never constrained so this 
> doesn't give much of an advantage. It would also be really useful to disable 
> this for MiniDFSCluster tests, since currently if you start a multi-DN 
> cluster and write with replication level 1, all of the replicas go to the 
> same DN.
> _[per discussion below, this was changed to not add a config, but only to add 
> a hook for testing]_

--
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

        

Reply via email to