You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of gRPC and what language are you using?
Version: 2.66.0
Language: C#
What operating system (Linux, Windows,...) and version?
Linux
What runtime / compiler are you using (e.g. .NET Core SDK version dotnet --info)
.NET SDK 8.0
What did you do?
We integrated gRPC .NET libraries to facilitate unary RPC calls between our services. While client-server communication generally works well with gRPC requests executing successfully, we occasionally encounter a potential deadlock. It looks like the issue arises when a subchannel state update occurs simultaneously after the completion of a request and a periodic DNS resolver attempting to update the same subchannel state.
What did you expect to see?
No deadlocks during the gRPC communication
What did you see instead?
Deadlock can be confirmed with the following stack traces of two stuck threads:
What version of gRPC and what language are you using?
Version: 2.66.0
Language: C#
What operating system (Linux, Windows,...) and version?
Linux
What runtime / compiler are you using (e.g. .NET Core SDK version
dotnet --info
).NET SDK 8.0
What did you do?
We integrated gRPC .NET libraries to facilitate unary RPC calls between our services. While client-server communication generally works well with gRPC requests executing successfully, we occasionally encounter a potential deadlock. It looks like the issue arises when a subchannel state update occurs simultaneously after the completion of a request and a periodic DNS resolver attempting to update the same subchannel state.
What did you expect to see?
No deadlocks during the gRPC communication
What did you see instead?
Deadlock can be confirmed with the following stack traces of two stuck threads:
Following stack trace analysis captured:
The text was updated successfully, but these errors were encountered: