[
https://issues.apache.org/jira/browse/MAPREDUCE-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083010#comment-13083010
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2787:
----------------------------------------------------
Just to give more clarity to what Arun said: even though there are patches on
MR-279 branch which implement the uber-task feature for the classic runtime
(JT/TT), those patches are not going to be ported to trunk when we merge MR-279
to trunk. OTOH, the uber-task feature for yarn+MR runtime is implemented via
LocalContainerAllocator and LocalContainerLauncher which is what you should
look at.
bq. Should we close this as won't fix?
+1. Ahmed, please close this once you are convinced. Thanks!
> MR-279: Performance improvement in running Uber MapTasks
> --------------------------------------------------------
>
> Key: MAPREDUCE-2787
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2787
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Reporter: Ahmed Radwan
> Assignee: Ahmed Radwan
> Attachments: MAPREDUCE-2787.patch
>
>
> The runUberMapTasks() in org.apache.hadoop.mapred.UberTask obtains the local
> fileSystem and local job configuration for every task attempt. This will
> have a negative performance impact.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
