Details
-
Improvement
-
Resolution: Won't Fix
-
Minor
-
0.8.0, 1.0.0
Description
For Production we recommend setting ulmits
docker run -d --ulimit nofile=40960:40960 --ulimit core=100000000:100000000 --ulimit memlock=100000000:100000000 --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase |
However there doesn't appear to be a way to pass these Args into the container from Pod. It appears support for this is still pending in kubernetes core. https://github.com/kubernetes/kubernetes/issues/3595#issuecomment-378120067
Here are the default ulimits set (minkube deployment)
ulimit -a
|
|
|
core file size (blocks, -c) unlimited
|
|
|
data seg size (kbytes, -d) unlimited
|
|
|
scheduling priority (-e) 0 |
|
|
file size (blocks, -f) unlimited
|
|
|
pending signals (-i) 23096 |
|
|
max locked memory (kbytes, -l) 64 |
|
|
max memory size (kbytes, -m) unlimited
|
|
|
open files (-n) 1048576 |
|
|
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) unlimited
|
|
|
virtual memory (kbytes, -v) unlimited
|
|
|
file locks (-x) unlimited
|
Maxfiles should be unlimited, but is 64!
As this can cause issues under heavy load we'll need to figure out the way to set limits.
Attachments
Issue Links
- relates to
-
K8S-454 Document ulimit settings for Kubernetes node
-
- Resolved
-