hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5236) references to JobConf.DISABLE_MEMORY_LIMIT don't make sense in the context of MR2
Date Mon, 13 May 2013 17:13:17 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656130#comment-13656130
] 

Sandy Ryza commented on MAPREDUCE-5236:
---------------------------------------

I didn't mean to suggest removing the constant, just references to it within the code.

Sure, I can do this in MAPREDUCE-5130.
                
> 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

Mime
View raw message