[
https://issues.apache.org/jira/browse/MAPREDUCE-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528766#comment-13528766
]
Jerry Chen commented on MAPREDUCE-4810:
---------------------------------------
+1 It makes sense separating stable confs with those that may vary by each job.
While the question is that how strong is the need to set per job confs (such as
Heap size) on a MRAppMaster that only masters the running of the tasks but not
running task itself. What I can think of is that different jobs may differ on
the number of tasks which may lead different level of memory comsumption. Is
there any other use cases that may have a specific need of heap size of
MRAppMaster?
> Add admin command options for ApplicationMaster
> -----------------------------------------------
>
> Key: MAPREDUCE-4810
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4810
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: applicationmaster
> Affects Versions: 2.0.2-alpha, 0.23.4
> Reporter: Jason Lowe
> Priority: Minor
>
> It would be nice if the MR ApplicationMaster had the notion of admin options
> in addition to the existing user options much like we have for map and reduce
> tasks, e.g.: mapreduce.admin.map.child.java.opts vs. mapreduce.map.java.opts.
> This allows site-wide configuration options for MR AMs but still allows a
> user to easily override the heap size of the AM without worrying about
> dropping other admin-specified options.
--
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
