[
https://issues.apache.org/jira/browse/MAPREDUCE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742681#action_12742681
]
Sreekanth Ramakrishnan commented on MAPREDUCE-478:
--------------------------------------------------
Also on second thought, in my opinion
[HADOOP-6105|http://issues.apache.org/jira/browse/HADOOP-6105] actually helps
the issue which is mentioned here, it provides you automatic facility to split
old key into two new keys.
> 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.
