You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2012/09/17 10:47:08 UTC

[jira] [Commented] (HADOOP-8817) Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1

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

Junping Du commented on HADOOP-8817:
------------------------------------

Thanks Suresh for the correction here. So branch-1.2 is next feature branch (1.1 is next bug-fix branch). Isn't it?
                
> Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-8817
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8817
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 1.0.0
>            Reporter: Junping Du
>            Assignee: Junping Du
>              Labels: features
>         Attachments: HADOOP-8817.patch
>
>
> HADOOP-8468 propose network topology changes for running on virtualized infrastructure, which includes:
> 1. Add "NodeGroup" layer in new NetworkTopology (also known as NetworkTopologyWithNodeGroup): HADOOP-8469, HADOOP-8470
> 2. Update Replica Placement/Removal Policy to reflect new topology layer: HDFS-3498, HDFS-3601
> 3. Update balancer policy:HDFS-3495
> 4. Update Task Scheduling Policy to reflect new topology layer and support the case that compute nodes (NodeManager or TaskTracker) and data nodes are separated into different VMs, but still benefit from physical host locality: YARN-18, YARN-19.
> This JIRA will address the backport work on branch-1 which will be divided into 4 issues/patches in related jira issues.

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