Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Resilience Pillar/ Rapid Fault Recovery/ RES09 Retries After Failures/ RES09-03 Avoiding Creating Too Much Traffic Pressure from Excessive Retries
Updated on 2025-05-22 GMT+08:00
RES09-03 Avoiding Creating Too Much Traffic Pressure from Excessive Retries
Retries from the client work well for temporary faults caused by intermittent disconnections. However, for faults caused by a sudden traffic spike, a retry may worsen the situation, which needs to be avoided.
- Risk level
High
- Key strategies
When the client retries requests, you are advised to:
- Add exponential backoff with jitter to avoid traffic pressure on the server. Exponential backoff increases the delay between retries exponentially. Jitter introduces randomness to the delay interval between two retries and avoids retry peaks at the same time.
- Limit the maximum number of retries or retry interval to prevent traffic spikes caused by message backlog.
Parent topic: RES09 Retries After Failures
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot