You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Vladimir Klimontovich (JIRA)" <ji...@apache.org> on 2010/08/18 22:47:27 UTC
[jira] Resolved: (MAPREDUCE-2003) It should be able to specify
different jvm settings for map and reduce child process (via
mapred.child.map.java.opts and mapred.child.reduce.java.opts options)
[ https://issues.apache.org/jira/browse/MAPREDUCE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Klimontovich resolved MAPREDUCE-2003.
----------------------------------------------
Resolution: Duplicate
Yep, MAPREDUCE-1207 is exactly the same. Sorry for duplicate bug, closing
> It should be able to specify different jvm settings for map and reduce child process (via mapred.child.map.java.opts and mapred.child.reduce.java.opts options)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2003
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2003
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: tasktracker
> Reporter: Vladimir Klimontovich
> Fix For: 0.20.3, 0.21.0, 0.22.0
>
>
> Sometimes mapper child process requires different JVM settings than reducer. For example when mapper requires much more memory than reducer.
> Now it's only possible to set options for both using mapred.child.java.opts.
> Proposed solution: mapred.child.java.opts could be overwritten by mapred.child.map.java.opts or mapred.child.reduce.java.opts. Thus, we're adding more flexibility and compatibility with old configurations.
> The same should be done for mapred.child.env.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.