hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9253) Capture ulimit info in the logs at service start time
Date Sat, 26 Jan 2013 20:25:12 GMT

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

Harsh J commented on HADOOP-9253:
---------------------------------

Also to note, its better to rely on the proc-fs limits file than the ulimit command run by
the launching user: the former's more truthful in face of PAM config oddities.
                
> 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
>         Attachments: HADOOP-9253.branch-1.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

Mime
View raw message