[
https://issues.apache.org/jira/browse/MAPREDUCE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-478:
------------------------------------
Status: Open (was: Patch Available)
On second thoughts, I think we should not add
mapred.{map|reduce}.child.{java.opts|env|ulimit} to mapred-default.xml since we
want to be backward compatible with existing configs with
mapred.child.{java.opts|env|ulimit}. Thoughts?
I'll upload a new patch without any changes to mapred-default.xml...
> separate jvm param for mapper and reducer
> -----------------------------------------
>
> Key: MAPREDUCE-478
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-478
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Koji Noguchi
> Assignee: Arun C Murthy
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HADOOP-5684_0_20090420.patch,
> MAPREDUCE-478_0_20090804.patch, MAPREDUCE-478_0_20090804_yhadoop20.patch
>
>
> Memory footprint of mapper and reducer can differ.
> It would be nice if we can pass different jvm param (mapred.child.java.opts)
> for mappers and reducers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
