hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3566) MR AM slows down due to repeatedly constructing ContainerLaunchContext
Date Thu, 15 Dec 2011 20:01:31 GMT

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

Vinod Kumar Vavilapalli updated MAPREDUCE-3566:

    Attachment: MAPREDUCE-3566-20111215.txt

A very raw patch that I was using during the performance testing.

Will clean it up and add tests if any possible.
> MR AM slows down due to repeatedly constructing ContainerLaunchContext
> ----------------------------------------------------------------------
>                 Key: MAPREDUCE-3566
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3566
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>             Fix For: 0.23.1
>         Attachments: MAPREDUCE-3566-20111215.txt
> The construction of the context is expensive, includes per-task trips to NameNode for
obtaining the information about job.jar, job splits etc which is redundant across all tasks.
> We should have a common job-level context and a task-specific context inheriting from
the common job-level context.

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


View raw message