[ https://issues.apache.org/jira/browse/HDFS-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junping Du reopened HDFS-3601: ------------------------------ Reopen issue to backport to branch-2. > Implementation of ReplicaPlacementPolicyNodeGroup to support 4-layer network > topology > ------------------------------------------------------------------------------------- > > Key: HDFS-3601 > URL: https://issues.apache.org/jira/browse/HDFS-3601 > Project: Hadoop HDFS > Issue Type: New Feature > Components: namenode > Reporter: Junping Du > Assignee: Junping Du > Fix For: 3.0.0 > > Attachments: > HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl.patch, > HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl-v2.patch, > HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl-v3.patch, > HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl-v4.patch, > HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl-v5.patch, > HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl-v6.patch, > HDFS-3601-branch-2.patch > > > A subclass of ReplicaPlacementPolicyDefault, ReplicaPlacementPolicyNodeGroup > was developed along with unit tests to support the four-layer hierarchical > topology. > The replica placement strategy used in ReplicaPlacementPolicyNodeGroup > virtualization is almost the same as the original one. The differences are: > 1. The 3rd replica will be off node group of the 2nd replica > 2. If there is no local node available, the 1st replica will be placed on a > node in the local node group. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira