-
Notifications
You must be signed in to change notification settings - Fork 82
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
net-kourier-controller component liveliness probe Failing #840
Comments
Could you please try to get the goroutine dump? 1. Enable debug log and profile options.
You should see the following logs after eanbling.
2. (After the controller hung up) port forward & dump 3 times.
After that, please share the output of |
@nak3 see data below generated
|
Thank you for the dump. But did you collect the data as instructed above? I think we need to see the dump 3 times with 5 sec internal to see which threads hung. Also pod logs + CPU usage on the host is useful.
|
Also experiencing this. We have nearly 9k knative services / ingresses defined. Kubernetes and knative as a whole are basically fine with this, but one little snag is that it takes ~4 hours for kourier to finish its Looks like more info is requested, I'll see if I can help to provide it. |
With debug output on, we get more information after the
CPU usage is measurable/more than zero but less than 1% of a core. Three full pprof dumps about 5 seconds apart:
|
This issue is stale because it has been open for 90 days with no |
This issue or pull request is stale because it has been open for 90 days with no activity. This bot triages issues and PRs according to the following rules:
You can:
/lifecycle stale |
This issue is stale because it has been open for 90 days with no |
Having an issue with net-kourier-knative liveliness probe failing. Describe the pod gives this data
logs from the pod
The text was updated successfully, but these errors were encountered: