Actions
Task #11745
closed
node14-d-d4s.d4science.org: Increase file descriptor limit to 16000 on registry service instance
Start date:
May 09, 2018
Due date:
% Done:
100%
Estimated time:
Infrastructure:
Development
Description
As done in production, it's needed to increase the file descriptor limit to 16000 in order to avoid the TooManyOpenFiles exception.
Now the ulimit is set to 1024 on that VM:
gcube2@node14-d-d4s:~$ ulimit -n 1024
Updated by Andrea Dell'Amico almost 7 years ago
- Status changed from New to In Progress
- Assignee changed from _InfraScience Systems Engineer to Roberto Cirillo
- % Done changed from 0 to 90
Done. The service must be restarted to inherit the change.
Next time you can apply the change by yourself, running the appropriate playbook with the label -t pam_limits
Updated by Roberto Cirillo almost 7 years ago
- Subject changed from node14-d-d4s.d4science,iorg: Increase file descriptor limit to 16000 on registry service instance to node14-d-d4s.d4science.org: Increase file descriptor limit to 16000 on registry service instance
Updated by Roberto Cirillo almost 7 years ago
- Status changed from In Progress to Feedback
- Assignee changed from Roberto Cirillo to Andrea Dell'Amico
Andrea Dell'Amico wrote:
Done. The service must be restarted to inherit the change.
Next time you can apply the change by yourself, running the appropriate playbook with the label
-t pam_limits
I see the same limit:
gcube2@node14-d-d4s:~$ ulimit -n 1024
Maybe it's needed a VM restart?
Updated by Andrea Dell'Amico almost 7 years ago
No, I didn't notice that the user is gcube2 and not gcube. Now the limit applies to gcube2 too.
Updated by Roberto Cirillo almost 7 years ago
- Status changed from Feedback to Closed
- % Done changed from 90 to 100
Actions
