hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8817) Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1
Date Tue, 19 Mar 2013 17:39:17 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Luke Lu updated HADOOP-8817:

    Fix Version/s: 1.2.0
     Release Note: A new 4-layer network topology NetworkToplogyWithNodeGroup is available
to make Hadoop more robust and efficient in virtualized environment.
> 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
>             Fix For: 1.2.0
>         Attachments: HADOOP-8817.patch, HADOOP-8817-v2.patch, HADOOP-8817-v3.patch, HADOOP-8817-v4.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,
> 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

View raw message