[
https://issues.apache.org/jira/browse/HDFS-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-2825:
------------------------------
Attachment: hdfs-2825.txt
Simple patch - no direct tests included, but the test in HDFS-2826 uses this
new feature, and will fail if the config doesn't work correctly. The old code
path/behavior remains the same.
> Add config option 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
> Attachments: 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.
--
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
