-
Notifications
You must be signed in to change notification settings - Fork 56
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
Stream Removed #194
Comments
This happens in the Node client as well. Does the C# client use the Google C client under the hood? |
Actually this issue was covered also by a support case, for reference https://jira.camunda.com/browse/SUPPORT-8433 It seems to be related to grpc/grpc#15623 and grpc/grpc-node#708 |
I don't think that we can do anything here. If you want to retry these kind of calls your could try the new sendWithRetry methods, see https://github.com/camunda-community-hub/zeebe-client-csharp/blob/master/Client/Api/Commands/IFinalCommandWithRetryStep.cs Be aware that not all commands implement that yet |
Regarding your question @jwulf it seems so, output from the user agent: |
I think we could overcome this with switching to dotnet-grpc, which is available for .net core 3.0 https://grpc.io/blog/grpc-on-dotnetcore/ The question would be if we want to drop core 2.1 |
@Lamby123 which .net version do you use? Would be migrating the client to .net core 3.x or higher suitable to you? |
Describe the bug
Several times a day we get a "stream removed" error coming back from the Zeebe Client.
One or more errors occurred. (Status(StatusCode="Unknown", Detail="Stream removed", DebugException="Grpc.Core.Internal.CoreErrorDetailException: ................
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It looks like this is a known issue with certain versions of GRPC core libaries.
We would expect this error to be handled within the client and for the request to be retried, or for the version of GRPC to be updated to one that does not have this issue . (if there is one).
Enviroment (please complete the following information):
The text was updated successfully, but these errors were encountered: