[
https://issues.apache.org/jira/browse/MAPREDUCE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742261#action_12742261
]
Sreekanth Ramakrishnan commented on MAPREDUCE-478:
--------------------------------------------------
The patch currently does not apply on the trunk. The conflict is with
mapred-tutorial.xml
We are not currently supporting deprecation of {{mapred.task.child.env}}
variable whereas we are supporting deprecation of other variable.
Not related to this patch, there is no current documentation of
{{mapred.task.child.env}} but shouldn't we document
{{mapred.(map|reduce).child.env}}?
Also finally, shouldn't we have a test case to verify if we are having a proper
backward compatibility with the options which we are introducing?
> 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,
> MAPREDUCE-478_1_20090806.patch, MAPREDUCE-478_1_20090806_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.
