hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12283) CLONE - Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1
Date Thu, 30 Jul 2015 15:26:07 GMT

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

Junping Du commented on HADOOP-12283:

All branch-1 work has already been covered by HADOOP-8817, and get committed with 4 following
JIRAs that related to HADOOP-8817. The feature already released in 1.2.0, will close this
JIRA as duplicated.

> CLONE - Backport Network Topology Extension for Virtualization (HADOOP-8468) to branch-1
> ----------------------------------------------------------------------------------------
>                 Key: HADOOP-12283
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12283
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ha, io
>    Affects Versions: 1.0.0
>            Reporter: RacingDawn
>            Assignee: Junping Du
>              Labels: features
>             Fix For: 1.2.0
>         Attachments: 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 was sent by Atlassian JIRA

View raw message