We have system default ``open_files`` limit which is enough for human user but may harm service environment
keystone@node-85:~$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 256968 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 256968 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
We already had an issue resolved such a way: https://bugs.launchpad.net/fuel/+bug/1405657
We have system default ``open_files`` limit which is enough for human user but may harm service environment
keystone@node-85:~$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 256968
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 256968
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
We already had an issue resolved such a way: https:/ /bugs.launchpad .net/fuel/ +bug/1405657