You need to resolve the delivery API error.
What should you do?
You need to resolve the delivery API error.
What should you do?
To resolve the delivery API error effectively, implementing exponential backoff using the EnableRetryOnFailure feature of Entity Framework is the recommended approach. Exponential backoff will help mitigate the issue by reducing the retry attempts over time, preventing the system from being overwhelmed by too many retries in a short time period. This method adjusts the retry interval exponentially, which is more efficient and resilient against transient errors compared to simple retry or other patterns.
Don´t now why B and not A. https://social.technet.microsoft.com/Forums/en-US/209e6f88-8ac9-4bff-a898-323ac2f1f6e5/a-transport-level-level-error-has-occurred-when-receiving-results-from-the-server-error-19-?forum=ssdsgetstarted Another useful method to get rid of this error is to use RETRY LOGIC of Entity Framework 1.1.0 services.AddDbContext<DbContext>(options => options.UseSqlServer('yourconnectionstring', sqlServerOptionsAction: sqlOptions => { sqlOptions.EnableRetryOnFailure( maxRetryCount: 5, maxRetryDelay: TimeSpan.FromSeconds(30), errorNumbersToAdd: new List<int>() { 19 }); })); This is way to elevate I think
Given answer is CORRECT. Use - ExponentialBackoff class We recommend that you wait for 5 seconds before your first retry. Retrying after a delay shorter than 5 seconds risks overwhelming the cloud service. For each subsequent retry, the delay should grow exponentially, up to a maximum of 60 seconds.
B is ok
B is ok
B will avoid excessive retries saving on utilization and bandwidth the only difference between scenario the db server is going to take 1 min to become available Using method A it will try 12 times in that min while option B would try only 3 times
Answer is B. https://docs.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-connectivity-issues