-
Notifications
You must be signed in to change notification settings - Fork 68
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
Timeout while sending batch #100
Comments
The sender should handle reestablishing a connection and link upon failure. Have you noticed any network partitions between your service and Event Hubs? If possible, it would be great to run the client with tracing on. The library is instrumented using OpenCensus. Should be able to visualize a trace and see if there are any errors similar to what was done in #81. Also, you can run the service with env With that information, we should be able to quickly determine the root cause. |
We are also seeing errrors "amqp: link closed" and "amqp: connection closed". After som digging into the code it seems like the recovering is not happening for these cases. In the trySend method in sender.go the errors above is hitting the default case and is not recovered since they are created with
|
I think this is related: Azure/azure-service-bus-go#116 I'll get a fix in by the end of the week. |
Hi @devigned, any updates on the fix? |
Sorry for the delay. Should get this pulled in shortly. |
Please grab |
We have a microservice running that sends one message to an eventhub every second. We're seeing timeouts (context.deadlineExceeded) in this setup multiple times per day with a timeoutCtx of 5 seconds. Sometimes it helps to create a new hub object, at other times sending the subsequent message also fails with the same timeout and error. We have another microservice written in Java that has a similar logic where we don't see this behaviour.
Until now we saw these errors:
Are there any options we can try out, how should we deal with reconnecting?
Environment
The text was updated successfully, but these errors were encountered: