You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2013/02/08 22:45:13 UTC
[jira] [Reopened] (HADOOP-9253) Capture ulimit info in the logs at
service start time
[ https://issues.apache.org/jira/browse/HADOOP-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur reopened HADOOP-9253:
----------------------------------------
Now, when starting the cluster you get on the console
{code}
ulimit -a for user tucu
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 709
virtual memory (kbytes, -v) unlimited
{code}
The OUT file is created on every start and that is the only thing you get, on every service.
I think we should remove the *head -30*.
> Capture ulimit info in the logs at service start time
> -----------------------------------------------------
>
> Key: HADOOP-9253
> URL: https://issues.apache.org/jira/browse/HADOOP-9253
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.1.1, 2.0.2-alpha
> Reporter: Arpit Gupta
> Assignee: Arpit Gupta
> Fix For: 1.2.0, 0.23.7, 2.0.4-beta
>
> Attachments: HADOOP-9253.branch-1.patch, HADOOP-9253.branch-1.patch, HADOOP-9253.branch-1.patch, HADOOP-9253.patch, HADOOP-9253.patch
>
>
> output of ulimit -a is helpful while debugging issues on the system.
--
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