hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (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 03:01:17 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-5236:
----------------------------------------------------

JobConf.DISABLED_MEMORY_LIMIT is unfortunately a public constant in MR1. Can't remove it.

We should definitely update the defaults, but that can be done in MAPREDUCE-5130 itself?

Overall, I see in general that if someone sets a -1 for these, the apps will no longer work
in MR2. This is a compatibility breakage which we cannot fix. We can just document it on that
documentation JIRA.
                
> 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