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
The only place where retries make most sense for streaming receiver is to ensure that for retryable errors, we bring up the receiver link behind the scenes and resume receiving events without bothering the user.
For such a case, we currently use a much higher "retryAttempts" to ensure that we cover the case of intermittent network loss. The problem with using a client level default for such scenario is that such defaults are usually low and won't serve the purpose outlined in the previous line.
Proposal is to have a separate kind of a retry options that are specifically used for re-establishing failed AMQP links or connections.
As per the API proposal in #2718 (comment), we will now have a createReceiver() method on the Event Hub Client that returns a receiver. It is on this method that we will be allowing retry options rather than individual operations.
Allow users to configure retry options in the streaming receiver as described in #2661 (comment)
Using retries for the creation of receiver link is covered in #2835
The text was updated successfully, but these errors were encountered: