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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/01/14 09:43:48 UTC

[jira] Updated: (MAPREDUCE-1085) For tasks, "ulimit -v -1" is being run when user doesn't specify mapred.child.ulimit

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

Todd Lipcon updated MAPREDUCE-1085:
-----------------------------------

    Attachment: mapreduce-1085.txt

Patch simply sets the ulimit command to null if it's set to <=0

Unfortunately this is very difficult to get to via a new unit test since it's deep within private methods, but should be straightforward and the code is covered by lots of integration tests.

> For tasks, "ulimit -v -1" is being run when user doesn't specify mapred.child.ulimit
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1085
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1085
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Ravi Gummadi
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: mapreduce-1085.txt
>
>
> For tasks, "ulimit -v -1" is being run when user doesn't specify mapred.child.ulimit.  Taking -1 as default value and using it in building the command is not right.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.