-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Healthcheck error - i/o timeout #4210
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
Comments
Have you manage to fix this? I have the same issue with 0.24.1. |
We saw this issue recently. It appeared to be that our worker nodes were overloaded. We think kubernetes was trying to keep everything alive but ended up killing other services in the process. We added two nodes and haven't had the problem since. |
I set a workaround by increasing the health check timeout values. This seemed to give it a chance to settle down and since then no issues. |
@richstokes what timeouts are working for you? |
I just doubled whatever they were set to. |
We tried guaranteeing a whole CPU and 1GB memory per and that changed nothing. We are also running ModSecurity, I thought it was load via that but maybe unrelated. |
Closing. This is fixed in master #4487 |
Uh oh!
There was an error while loading. Please reload this page.
This is a
kops
provisioned cluster, running on AWS. The nginx controllers seem OK until they receive some traffic, and then they crash with the above errors. Sometimes the controllers will stay up for a period of time. It seems fairly random. Host resources are OK.Sometimes I have also seen in the log
E0618 21:57:07.096186 8 checker.go:57] healthcheck error: 500
Strange thing is this configuration has been working great for months, we've not changed anything. Is there anything else I can check on our side?
The text was updated successfully, but these errors were encountered: