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 "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/05/12 05:41:16 UTC
[jira] [Updated] (MAPREDUCE-5236) references to
JobConf.DISABLE_MEMORY_LIMIT don't make sense in the context of MR2
[ https://issues.apache.org/jira/browse/MAPREDUCE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandy Ryza updated MAPREDUCE-5236:
----------------------------------
Description: In MR1, a special value of -1 could be given for mapreduce.job.map|reduce.memory.mb when memory limits were disabled. In MR2, this makes no sense, as with slots gone, this value is used for requesting resources and scheduling. (was: In MR1, a special value of -1 could be given for mapreduce.job.map|reduce.memory.mb to disable memory limits. In MR2, this makes no sense, as with slots gone, this value is used for requesting resources and scheduling.)
> references to JobConf.DISABLE_MEMORY_LIMIT don't make sense in the context of MR2
> ---------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5236
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5236
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> In MR1, a special value of -1 could be given for mapreduce.job.map|reduce.memory.mb when memory limits were disabled. In MR2, this makes no sense, as with slots gone, this value is used for requesting resources and scheduling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira