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

Junping Du commented on HADOOP-8468:
------------------------------------

I start the work to backport NodeGroup-aware topology to branch-2, there are 7 
patches below in Common & HDFS:
patch 1 - HADOOP-8469: make NetworkTopology pluggable
patch 2 - HADOOP-8470: implementation of NetworkTopologyWithNodeGroup
patch 3 - HDFS-3498: Make BlockPlacementPolicyWithDefault extensible and Block 
Placement Removal policy extensible
patch 4 - HDFS-3601: implementation of BlockPlacementPolicyWithNodeGroup
patch 5 - HDFS-4240: fix a bug in nodegroup-aware case
patch 6 - HDFS-3495: Make Balancer support node group layer
patch 7 - HDFS-4261: Fix a timeout issue in TestBalancerWithNodeGroup case

                
> Umbrella of enhancements to support different failure and locality topologies
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-8468
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8468
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ha, io
>    Affects Versions: 1.0.0, 2.0.0-alpha
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: HADOOP-8468-total.patch, HADOOP-8468-total-v3.patch, 
> HVE_Hadoop World Meetup 2012.pptx, HVE User Guide on branch-1(draft ).pdf, 
> Proposal for enchanced failure and locality topologies.pdf, Proposal for 
> enchanced failure and locality topologies (revised-1.0).pdf
>
>
> 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.

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

Reply via email to