[
https://issues.apache.org/jira/browse/HADOOP-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564053#comment-13564053
]
Harsh J commented on HADOOP-9253:
---------------------------------
PAM is the one that applies limits (pam_limits.so) and PAM is configurable in
how it applies to various scenarios it needs to be on. See
http://linux.die.net/man/8/pam_limits, which also states that things may be
changed to suit different needs in an environment (i.e. "For the services you
need resources limits (login for example) put a the following line in
/etc/pam.d/login as the last line for that service (usually after the pam_unix
session line)")
We had been battling limit-induced issues at customers almost the whole of 2011
since at that time the config had to be manual, but Apache Bigtop and other
tools has solved it for us now by placing limits files during installation.
This is still good to go though, just want to make sure we aren't writing out
wrong values in any special case (such as a secure DN startup, particularly).
> 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
