-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
grpc-go/transport: "panic: send on closed channel" #8595
Comments
@zbindenren could you reproduce this issue with a simpler script as it will help me debug this for you? |
I am going to look into this soon. |
@fanminshi unfortunately it is not ease to reproduce. We get this issue since upgrading to the latest version. And it only happens when we have a lot of clients. We have a similar setup with a small number of clients and there we do not see the issue. |
@xiang90 @fanminshi @zbindenren This has been partially fixed in upstream grpc/grpc-go#1115. The fix is available since grpc-go v1.4.x. Which means we would have to wait until etcd v3.3 release. Root cause grpc/grpc-go#1111 hasn't been addressed, though. |
@gyuho thanks for the investigation. i marked this as a dependency issue. |
Thx for the info. Any plans when 3.3 is going to be released? |
closing. we already bumped gRPC to 1.6 in master to get this fixed. |
Hi
Since the upgrade to latest version 3.2.7, our server crashes every 1-2 days and we have to start it manually.
The error and stack:
And then after a while it is possible that the second server also crashes and only one cluster is available.
We have a three node setup, and around 2000 clients. We have around 6000 watch streams and arround 3000 lease streams. I think the grpc proxy might help, but because of #8162 we do not use it yet.
The text was updated successfully, but these errors were encountered: