hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9253) Capture ulimit info in the logs at service start time
Date Mon, 28 Jan 2013 16:47:14 GMT

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

Arpit Gupta commented on HADOOP-9253:
-------------------------------------

bq. Does this also work in context of a secure DN startup? Does the logged ulimit reflect
the actual JVM's instead of the wrapper's?


Good point let me test this out and see what it will log.
                
> 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