-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
panic: send on closed channel #6854
Comments
Thank you for reporting this issue. It looks like #6489 might be the culprit, but I'm not certain at this point. Needs more investigation. Do you have any way to reproduce this? |
Also, do you use the |
We don't now, unfortunately. We've just reverted this when we noticed the issue.
Yes, we do. We set this the same as GOMAXPROCS and pod's CPU requests/limits. |
Are the panics happening around the time when |
Yes, they are happening right after the |
What version of gRPC are you using?
1.60
What version of Go are you using (
go version
)?1.21.3
What operating system (Linux, Windows, …) and version?
cos_containerd on GKE
What did you do?
After upgrading from 1.59 to 1.60 we started to get panics from time to time. We didn't change anything else.
We use Proxyless Traffic Director in GCP.
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: