hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5130) Add missing job config options to mapred-default.xml
Date Fri, 10 May 2013 17:07:16 GMT

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

Sandy Ryza commented on MAPREDUCE-5130:

Thanks for taking a look, Vinod.

bq. Can you please file a ticket if the test is failing on trunk too? Tx.
Filed MAPREDUCE-5236

bq. mapreduce.job.jvm.numtasks isn't supported in MR over YARN. 
Oops. Will take this out.

bq. Instead of removing code for computeNumSlotsPer*, you can make it work with simple modifications?
computeNumSlotsPer* isn't used anywhere in the code. As there are no more slots in YARN, and
it is not a public API, would it not make the most sense to remove it?  I could fix the test
here and remove it later in MAPREDUCE-5236 if that would be better?

> 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,
> 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

View raw message