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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2013/05/12 01:55:15 UTC

[jira] [Commented] (MAPREDUCE-5236) JobConf should not support disabling memory limits

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

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

Even in MR1, mapreduce.job.map|reduce.memory.mb aren't used to disable the limits - their cluster counter parts are. If you give a -1, when memory monitoring is enabled on the cluster, the job will fail.

Given that, I don't see what you is proposing.
                
> JobConf should not support disabling memory limits
> --------------------------------------------------
>
>                 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 to disable memory limits.  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