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 "Arun C Murthy (JIRA)" <ji...@apache.org> on 2009/09/15 06:00:57 UTC

[jira] Created: (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

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
             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.