-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sysctlFSFileMax
not using fs.file-max
#2048
Comments
I found that we are now using following logic to get maximum number of open file descriptors, is it possible to update it via
|
sysctl -w fs.file-max=90000
does not take effect for initContainersysctlFSFileMax
not using fs.file-max
What do you mean? We read the value using the RLIMIT_NOFILE syscall (same thing than using sysctl) |
@gyliu513 Do you run |
Closing. Fixed in #2050 |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
NGINX Ingress controller version:
I was using ingress 0.9.0.
I updated the
initContainer
in ingress controller by addingsysctl -w fs.file-max=1608170
as following:And restart the ingress controller, but in the log, I found that the file max was still 65536.
Related source code here https://github.com/kubernetes/ingress-nginx/blob/nginx-0.9.0/internal/ingress/controller/nginx.go#L559:60
/cc @aledbf any comments for this? Thanks!
Kubernetes version (use
kubectl version
):Environment:
uname -a
):What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: