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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/19 00:12:06 UTC

[jira] [Resolved] (MAPREDUCE-187) Generalize mapred.child.ulimit so as to help setting up other limits.

     [ https://issues.apache.org/jira/browse/MAPREDUCE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-187.
----------------------------------------

    Resolution: Won't Fix

I'm going to close this as Won't Fix given the usage of cgroups and more.

> Generalize mapred.child.ulimit so as to help setting up other limits.
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-187
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-187
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>
> Currently mapred.child.ulimit cannot be used for anything other than for setting virtual limits. It is hardcoded to set virtual mem limits (ulimit -v) only. This should be changed so that other limits like open file descriptors, max user processes etc can be set.



--
This message was sent by Atlassian JIRA
(v6.2#6252)