hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5417) Propagate task settings to AM when job runs in uber mode
Date Wed, 24 Jul 2013 23:27:48 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719008#comment-13719008

Karthik Kambatla commented on MAPREDUCE-5417:

When the settings for map/reduce tasks conflict, it should be okay to set to the maximum value.
> 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

View raw message