-
Notifications
You must be signed in to change notification settings - Fork 51
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
conntrack hashsize alteration fails on large CPU counts #10
Comments
Oh wow, nice find. Could you send a PR with the steps to reduce the CPU count? (Please also FWIW, have you also tried the other suggested workarounds to pass On the host you should be able to write to echo "262144" > /sys/module/nf_conntrack/parameters/hashsize In order to not forget this, you should be able to put this into a |
Will try those workarounds, thanks! I'll try and get a PR for you soon. |
See kubernetes/kubernetes#58610
When the CPU count is large (e.g. I had it at 12 which is the amount on my host), conntrack hashsize may need to be increased when starting kube-proxy during k8s boot. The problem in LXC setups seems to be that the /sys/.../conntrack/hashsize file cannot be edited in any way inside the container, leading to failure if it needs to be altered.
My fix was to limit the CPU count on the system to 4 cores, which resulted in no wanted changes to the hashsize value.
Maybe add a note about this into the guide?
The text was updated successfully, but these errors were encountered: