Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0.0, 2.0.0-alpha
-
None
-
None
Description
The current hadoop network topology (described in some previous issues like: Hadoop-692) works well in classic three-tiers network when it comes out. However, it does not take into account other failure models or changes in the infrastructure that can affect network bandwidth efficiency like: virtualization.
Virtualized platform has following genes that shouldn't been ignored by hadoop topology in scheduling tasks, placing replica, do balancing or fetching block for reading:
1. VMs on the same physical host are affected by the same hardware failure. In order to match the reliability of a physical deployment, replication of data across two virtual machines on the same host should be avoided.
2. The network between VMs on the same physical host has higher throughput and lower latency and does not consume any physical switch bandwidth.
Thus, we propose to make hadoop network topology extend-able and introduce a new level in the hierarchical topology, a node group level, which maps well onto an infrastructure that is based on a virtualized environment.
Attachments
Attachments
Issue Links
- incorporates
-
HDFS-4240 In nodegroup-aware case, make sure nodes are avoided to place replica if some replica are already under the same nodegroup
- Closed
-
YARN-18 Configurable Hierarchical Topology for YARN
- Open
-
YARN-19 4-layer topology (with NodeGroup layer) implementation of Container Assignment and Task Scheduling (for YARN)
- Open
-
HDFS-3495 Update Balancer to support new NetworkTopology with NodeGroup
- Closed
-
HDFS-3601 Implementation of ReplicaPlacementPolicyNodeGroup to support 4-layer network topology
- Closed
-
HDFS-3498 Make Replica Removal Policy pluggable and ReplicaPlacementPolicyDefault extensible for reusing code in subclass
- Closed
- is related to
-
HDFS-4886 Override verifyBlockPlacement() API in BlockPlacementPolicyWithNodeGroup
- Resolved
-
HDFS-4898 BlockPlacementPolicyWithNodeGroup.chooseRemoteRack() fails to properly fallback to local rack
- Closed
- relates to
-
HADOOP-11326 documentation for configuring HVE: dfs.block.replicator.classname should be org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicyWithNodeGroup
- Resolved
-
HDFS-3564 Design enhancements to the pluggable blockplacementpolicy
- Resolved