You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/09/15 06:59:57 UTC
[jira] Commented: (MAPREDUCE-979)
JobConf.getMemoryFor{Map|Reduce}Task doesn't fallback to newer config knobs
when mapred.taskmaxvmem is set to DISABLED_MEMORY_LIMIT of -1
[ https://issues.apache.org/jira/browse/MAPREDUCE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755342#action_12755342 ]
Hemanth Yamijala commented on MAPREDUCE-979:
--------------------------------------------
To be clear, mapred-default in hadoop is updated to not have mapred.task.maxvmem. However, M/R applications like PIG could bundle their own mapred-default which, if not updated, would break.
> JobConf.getMemoryFor{Map|Reduce}Task doesn't fallback to newer config knobs when mapred.taskmaxvmem is set to DISABLED_MEMORY_LIMIT of -1
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-979
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-979
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker, tasktracker
> Affects Versions: 0.20.1
> Reporter: Arun C Murthy
> Priority: Blocker
> Fix For: 0.20.2
>
>
> JobConf.getMemoryFor{Map|Reduce}Task doesn't fallback to newer config knobs when mapred.taskmaxvmem is set to DISABLED_MEMORY_LIMIT of -1, this results in failed job-submissions when mapred-default.xml has the default value of -1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.