[
https://issues.apache.org/jira/browse/HDFS-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE moved HADOOP-8472 to HDFS-3601:
------------------------------------------------------
Component/s: (was: ha)
(was: io)
name-node
Affects Version/s: (was: 2.0.0-alpha)
(was: 1.0.0)
Key: HDFS-3601 (was: HADOOP-8472)
Project: Hadoop HDFS (was: Hadoop Common)
> 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: name-node
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments:
> 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,
> HADOOP-8472-BlockPlacementPolicyWithNodeGroup-impl.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
