hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-3) Set mapred.child.ulimit automatically to the value of the RAM limits for a job, if they are set
Date Tue, 22 Jul 2014 21:12:41 GMT

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

Allen Wittenauer resolved MAPREDUCE-3.
--------------------------------------

    Resolution: Fixed

Who sets ulimit anymore? No one. Why? cgroups and /proc-based memory limits. Closing as stale.

> Set mapred.child.ulimit automatically to the value of the RAM limits for a job, if they
are set
> -----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>
> Memory based monitoring and scheduling allow users to set memory limits for the tasks
of their jobs. This parameter is the total memory taken by the task, and any children it may
launch (for e.g. in the case of streaming). A related parameter is mapred.child.ulimit which
is a hard limit on the memory used by a single process of the entire task tree. For user convenience,
it would be sensible for the system to set the ulimit to atleast the memory required by the
task, if the user has specified the latter.



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

Mime
View raw message