Re: cloudfoundry file descriptor limit is too small
DEA's file descriptor limit and application's one are two different things.
An application's file descriptor limit is defined as a property of the
process of the application instance running in a warden container.
You can see it by the following procedure:
1. Log in to the DEA (`bosh ssh runner_z1/0` or something)
2. Become superuser (`sudo -i`)
3. Find running warden container ID (execute `ls -l
/var/vcap/data/warden/depot` and you may see the list of running warden
4. Log in to the target warden container
/var/vcap/data/warden/depot/*WARDEN-CONTAINER-ID*/run/wshd.sock --user vcap
/bin/bash`, you should replace "*WARDEN-CONTAINER-ID*" to the ID you've
5. Get the process ID of the application process (`cat /home/vcap/run.pid`)
6. Get the limit property of the process (`cat /proc/*PID*/limits`, of
course you should replace *PID* to the actual process ID)
7. Now you may see the value of the file descriptor limit on the line "Max
In my case, it was 16384.
This value is defined by the Cloud Controller property
"instance_file_descriptor_limit" , and the default is 16384 .
It seems large enough for me, but if you want to change the number, it can
be done by changing " cc.instance_file_descriptor_limit" in your BOSH
deployment manifest and redeploy Cloud Controller.
I think it cannot be changed per application .
peter huang wrote
I'm not a ...
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-cloudfoundry-file-descriptor-limit-is-too-small-tp5948p6084.html
Sent from the CF Dev mailing list archive at Nabble.com.