You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Junping Du (JIRA)" <ji...@apache.org> on 2012/06/04 20:02:23 UTC

[jira] [Moved] (MAPREDUCE-4309) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

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

Junping Du moved HADOOP-8474 to MAPREDUCE-4309:
-----------------------------------------------

    Affects Version/s:     (was: 2.0.0-alpha)
                           (was: 1.0.0)
                       1.0.0
                       2.0.0-alpha
                  Key: MAPREDUCE-4309  (was: HADOOP-8474)
              Project: Hadoop Map/Reduce  (was: Hadoop Common)
    
> Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4309
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4309
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha, 1.0.0
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: HADOOP-8474-ContainerAssignmentTaskScheduling-pluggable.patch
>
>
> There are several classes in YARN’s container assignment and task scheduling algorithms that relate to data locality which were updated to give preference to running a container on other locality besides node-local and rack-local (like nodegroup-local). This propose to make these data structure/algorithms pluggable, like: SchedulerNode, RMNodeImpl, etc. The inner class ScheduledRequests was made a package level class to it would be easier to create a subclass, ScheduledRequestsWithNodeGroup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira