[
https://issues.apache.org/jira/browse/MAPREDUCE-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722157#comment-13722157
]
Tsuyoshi OZAWA commented on MAPREDUCE-5417:
-------------------------------------------
bq. I suspect when there are conflicts in map vs. reduce task settings we have
to not run the job as uber or have some hybrid where we run the maps within the
AM and the reduces as separate tasks.
Or, yet another simple way is to add configurations for uber mode. e.g.:
passing environment variables to uber mode via mapreduce.uber.java.opts.
Anyway, we should document how AM selects options, because users can confuse it.
> 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
