[ https://issues.apache.org/jira/browse/MAPREDUCE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765637#action_12765637
]
Hudson commented on MAPREDUCE-979:
----------------------------------
Integrated in Hadoop-Mapreduce-trunk #112 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/112/])
> 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
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
> Fix For: 0.20.2
>
> Attachments: mapreduce-979-1-20.patch, mapreduce-979-1.patch, mapreduce-979-2.patch,
mapreduce-979-20-2.patch, mapreduce-979-20-3.patch, mapreduce-979-3.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.
|