Adding retry logic to Azure Function output binding for transient mode #293

vicancy · 2023-10-10T09:53:32Z

It is possible that REST API calls to Azure SignalR service failed with intermittent 5xx errors, and retry can success. Customers using output binding has no easy way to retry sending by themselves, we could add retry logic into output binding for 5xx errors for better user experience.

Add retry capability to REST client to handle transient errors. Tracking issue: Azure/azure-functions-signalrservice-extension#293 ## Add two retry modes: 1. Fixed delay 3. Exponential backoff delay （Do we need to add jitter to the delay?) ## For message APIs: Only the situations when HTTP status code > 500 are safe to retry. For 500 error, runtime returns 500 when timeout, so it's not safe to retry. ## For non-message APIs: The following situations are considered to be transient: 1. HTTP response status code 5xx or 408(Request timeout). 2. Request timeout with the timeout length configured as `ServiceManagerOptions.HttpClientTimeout`

Y-Sindo mentioned this issue Oct 17, 2023

Add retry capability to REST client to handle transient errors Azure/azure-signalr#1844

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adding retry logic to Azure Function output binding for transient mode #293

Adding retry logic to Azure Function output binding for transient mode #293

vicancy commented Oct 10, 2023 •

edited

Loading

Adding retry logic to Azure Function output binding for transient mode #293

Adding retry logic to Azure Function output binding for transient mode #293

Comments

vicancy commented Oct 10, 2023 • edited Loading

vicancy commented Oct 10, 2023 •

edited

Loading