[ https://issues.apache.org/jira/browse/MAPREDUCE-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685092#comment-13685092 ]
Sandy Ryza commented on MAPREDUCE-5130: --------------------------------------- Good catch on mapreduce.(map|reduce).env, I'll add that in. mapreduce.(map|reduce).child.java.opts are special in that we need to fall back to a separate config (mapred.child.java.opts) if they are not set. The relationship between mapreduce.(map|reduce).memory.mb and mapred.job.(map|reduce).memory.mb is a simple deprecation, which, IIUC, the code should handle correctly. We already expect it to in a variety of cases, such as mapreduce.job.maps. I just verified on a pseudo-distributed cluster that, with the patch, setting mapred.job.map.memory.mb takes effect. Are there situations I'm not thinking of where this would not work? > Add missing job config options to mapred-default.xml > ---------------------------------------------------- > > Key: MAPREDUCE-5130 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5130 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: documentation > Affects Versions: 2.0.4-alpha > Reporter: Sandy Ryza > Assignee: Sandy Ryza > Attachments: MAPREDUCE-5130-1.patch, MAPREDUCE-5130-1.patch, > MAPREDUCE-5130-2.patch, MAPREDUCE-5130-3.patch, MAPREDUCE-5130-4.patch, > MAPREDUCE-5130.patch, MAPREDUCE-5130.patch > > > I came across that mapreduce.map.child.java.opts and > mapreduce.reduce.child.java.opts were missing in mapred-default.xml. I'll do > a fuller sweep to see what else is missing before posting a patch. > List so far: > mapreduce.map/reduce.child.java.opts > mapreduce.map/reduce.memory.mb > mapreduce.job.jvm.numtasks > mapreduce.input.lineinputformat.linespermap > mapreduce.task.combine.progress.records -- 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