-
Notifications
You must be signed in to change notification settings - Fork 54
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Reconnect / retry mechanism #295
Comments
@richardpark-msft and I have discussed this in the past, but nothing has been implemented in this module yet. We do have retry/reconnect logic in our EventHubs and Service Bus modules. Here are a few links to the implementation in Service Bus. Note that some of the error conditions are specific to Service Bus, so if you're using a different broker then some of the logic won't apply. Retry loop for sending/receiving a message Conceptually it's not that different from your retry/reconnect mechanism. Wait for a message and if an error is received, determine if it requires a reconnect (you should add |
@DGuhr, I can't speak for why other libraries don't have retries, but some things in Azure this more complicated. For instance:
In the end most of our example designs just ended up having to be so general that it just ended up being more straightforward to handle it on a per-call-site basis. BTW, if you do find that hidden mechanism PLEASE LET US KNOW. :) |
Hi 馃憢
I have a question, as I could not find a reconnect/retry mechanism for this client yet. Is it planned to add a reconnect / retry mechanism, or do you have an example of a consumer that has a reconnect/retry mechanism?
Context:
I searched a bit for such thing, but all I found so-far is https://github.com/isayme/go-amqp-reconnect/blob/master/rabbitmq/rabbitmq.go which is for an amqp 0.9.1 client - and now due to the lack of results, I am questioning myself if we're completely on the wrong track here and there is a hidden mechanism we just don't know of 馃槄
Thanks!
The text was updated successfully, but these errors were encountered: