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 2013/10/24 01:12:42 UTC

[jira] [Moved] (MAPREDUCE-5593) Cleanup code for AssignMapsWithLocality() in RMContainerAllocator

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

Junping Du moved YARN-1163 to MAPREDUCE-5593:
---------------------------------------------

    Component/s:     (was: applications)
                 applicationmaster
            Key: MAPREDUCE-5593  (was: YARN-1163)
        Project: Hadoop Map/Reduce  (was: Hadoop YARN)

> Cleanup code for AssignMapsWithLocality() in RMContainerAllocator
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-5593
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5593
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Minor
>         Attachments: YARN-1163-v1.patch, YARN-1163-v2.patch
>
>
> In RMContainerAllocator, AssignMapsWithLocality() is a very important method to assign map tasks on allocated containers with conforming different level of locality (dataLocal, rackLocal, etc.). However, this method messed with different code logic to handle different type of locality but have lots of similar behaviours. This is hard to maintain as well as do extension with other locality type, so we need some more clear code here.



--
This message was sent by Atlassian JIRA
(v6.1#6144)