[
https://issues.apache.org/jira/browse/MAPREDUCE-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718883#comment-13718883
]
Jason Lowe commented on MAPREDUCE-5417:
---------------------------------------
There's some issues with what to do if properties conflict (e.g.: different
environment settings for map vs. reduce tasks), but it would be nice if in the
common case the client code could make some smart decisions re: AM settings so
only enabling uber mode would "just work".
> Propagate task settings to AM when job runs in uber mode
> --------------------------------------------------------
>
> Key: MAPREDUCE-5417
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5417
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 2.0.4-alpha
> Reporter: Jason Lowe
>
> When a job runs in Uber-AM mode the JVM settings (e.g.: heap sizing),
> container sizing, and environment variables are not propagated to the AM.
> This means running in uber-AM mode is not as simple as enabling
> {{mapreduce.job.ubertask.enable}} since lack of proper heap/container
> settings can doom the AM to crash or lack of proper environment variables can
> prevent the task code from properly running.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
