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 "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org> on 2009/10/08 04:50:31 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=12763337#action_12763337 ]
Sreekanth Ramakrishnan commented on MAPREDUCE-979:
--------------------------------------------------
The changes look fine to me.
> 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
>
> Attachments: mapreduce-979-1-20.patch, mapreduce-979-1.patch, mapreduce-979-2.patch
>
>
> 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.