Help Center/
Well-Architected Framework/
Well-Architected Framework and Practices/
Resilience Pillar/
Cloud Service Reliability/
TaurusDB/
Common Faults
Updated on 2025-05-22 GMT+08:00
Common Faults
Excessive CPU, Memory, Disk, or Database Connection Usage or Disk IOPS on a TaurusDB Instance
- Check: Use Cloud Eye to check the CPU, memory, disk, or database connection usage or disk IOPS.
- Recovery:
- Change the specifications to expand resources based on service requirements.
- Enable auto scaling so that the specifications can be automatically upgraded or read replicas can be automatically added when an instance is overloaded.
- Enable overload protection for the application layer to keep high-priority services running smoothly.
Failed to Connect to a Backend TaurusDB Instance
- Check: Network connection failed.
- Recovery:
- If this is a temporary failure, for example, a primary/standby switchover is in progress, connect to the TaurusDB instance again at the application layer. For details, see RES09 Retries After Failures.
- If the connection to an overloaded TaurusDB instance failed, rectify the fault by referring to "Excessive CPU, Memory, Disk, or Database Connection Usage or Disk IOPS on a TaurusDB Instance."
Parent topic: TaurusDB
Feedback
Was this page helpful?
Provide feedbackThank 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