No, it doesn't. We `ulimit -n 10240` in our start script and it works just fine.
Where do you set the raised limit? Apparently upstart ignores limits.conf and you need to set this in your job definition: http://bryanmarty.com/2012/02/10/setting-nofile-limit-upstart/ /MR On Wed, Nov 30, 2016 at 10:23 PM <[email protected]> wrote: > Here is why? > root@ovrh0301:/home/envi# 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) 772117 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 100000 > pipe size (512 bytes, -p) 8 > ----------------------------------------- > envi@ovrh0301:~$ ps aux | grep kube-apiserver > root 3539 5.5 0.1 300696 252292 ? Ssl 11:09 10:26 > /opt/bin/kube-apiserver --insecure-bind-address=0.0.0.0 > --insecure-port=8080 --etcd-servers=http://127.0.0.1:4001 > --logtostderr=true --service-cluster-ip-range=192.168.3.0/24 > --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,SecurityContextDeny,DefaultStorageClass,ResourceQuota > --service-node-port-range=30000-32767 --advertise-address=172.31.0.200 > --allow-privileged=false --client-ca-file=/srv/kubernetes/ca.crt > --tls-cert-file=/srv/kubernetes/server.cert > --tls-private-key-file=/srv/kubernetes/server.key > envi 5546 0.0 0.0 11748 2164 pts/0 S+ 14:18 0:00 grep > --color=auto kube-apiserver > envi@ovrh0301:~$ > ------------------------------------------- > root@ovrh0301:/home/envi# cat /proc/3539/limits > Limit Soft Limit Hard Limit Units > Max cpu time unlimited unlimited seconds > Max file size unlimited unlimited bytes > Max data size unlimited unlimited bytes > Max stack size 8388608 unlimited bytes > Max core file size 0 unlimited bytes > Max resident set unlimited unlimited bytes > Max processes 772117 772117 > processes > Max open files 1024 4096 files > Max locked memory 65536 65536 bytes > --------------- > envi@ovrh0301:~$ sudo ls -l /proc/3539/fd > total 0 > lrwx------ 1 root root 64 Nov 30 14:08 0 -> /dev/null > lrwx------ 1 root root 64 Nov 30 14:08 1 -> /dev/pts/7 > lrwx------ 1 root root 64 Nov 30 14:08 10 -> socket:[69672] > lrwx------ 1 root root 64 Nov 30 14:08 100 -> socket:[69680] > lrwx------ 1 root root 64 Nov 30 14:08 1000 -> socket:[43353] > lrwx------ 1 root root 64 Nov 30 14:08 1001 -> socket:[73034] > lrwx------ 1 root root 64 Nov 30 14:08 1002 -> socket:[89431] > lrwx------ 1 root root 64 Nov 30 14:08 1003 -> socket:[86357] > lrwx------ 1 root root 64 Nov 30 14:08 1004 -> socket:[31818] > lrwx------ 1 root root 64 Nov 30 14:08 1005 -> socket:[86359] > lrwx------ 1 root root 64 Nov 30 14:08 1006 -> socket:[76133] > lrwx------ 1 root root 64 Nov 30 14:08 1007 -> socket:[75086] > lrwx------ 1 root root 64 Nov 30 14:08 1008 -> socket:[89433] > lrwx------ 1 root root 64 Nov 30 14:08 1009 -> socket:[73039] > lrwx------ 1 root root 64 Nov 30 14:08 101 -> socket:[11624] > lrwx------ 1 root root 64 Nov 30 14:08 1010 -> socket:[43394] > lrwx------ 1 root root 64 Nov 30 14:08 1011 -> socket:[75091] > lrwx------ 1 root root 64 Nov 30 14:08 1012 -> socket:[43358] > lrwx------ 1 root root 64 Nov 30 14:08 1013 -> socket:[44369] > lrwx------ 1 root root 64 Nov 30 14:08 1014 -> socket:[86361] > lrwx------ 1 root root 64 Nov 30 14:08 1015 -> socket:[73042] > lrwx------ 1 root root 64 Nov 30 14:08 1016 -> socket:[18776] > lrwx------ 1 root root 64 Nov 30 14:08 1017 -> socket:[73045] > lrwx------ 1 root root 64 Nov 30 14:08 1018 -> socket:[76135] > lrwx------ 1 root root 64 Nov 30 14:08 1019 -> socket:[65864] > lrwx------ 1 root root 64 Nov 30 14:08 102 -> socket:[31093] > lrwx------ 1 root root 64 Nov 30 14:08 1020 -> socket:[44371] > lrwx------ 1 root root 64 Nov 30 14:08 1021 -> socket:[89437] > lrwx------ 1 root root 64 Nov 30 14:08 1022 -> socket:[75097] > lrwx------ 1 root root 64 Nov 30 14:08 1023 -> socket:[73048] > lrwx------ 1 root root 64 Nov 30 14:08 103 -> socket:[36939] > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
