Error Description
Symptom 1: the execution latency was high.
Symptom 2: the business was affected.
Common Causes
The total number of requests was too high.
The traffic and connections were restricted.
There were complex commands such as KEYS * and MGET.
There are big keys and hot keys.
Cross-AZ or cross-Region access.
Bandwidth throttling.
Connection limit exceeded.
There is network jitter.
Solution
You can check whether the above problems exist based on the monitoring data in the console and your own business logic and make targeted optimizations.
Troubleshooting Procedure
3. Optimize complex commands. If there is a KEYS *command, you can consider using the SCAN command to traverse in batches instead of using KEYS with a higher time complexity. If there is an MGET command, you can consider splitting it into n operations to get n keys.