Help Center/
Well-Architected Framework/
Well-Architected Framework and Practices/
Resilience Pillar/
Cloud Service Reliability/
DMS/
Common Faults
Updated on 2025-05-22 GMT+08:00
Common Faults
Excessive CPU, Memory, Disk, or Bandwidth Usage
- Check: Use Cloud Eye to check the CPU, memory, disk, or bandwidth usage.
- Recovery:
- If the CPU or memory usage is high, change the broker specifications or add brokers to expand resources based on service requirements.
- If the disk usage is high, scale up the instance storage based on service requirements.
- If the bandwidth usage is high, change the specifications to support higher bandwidth based on service requirements.
- Enable overload protection for the application layer to keep high-priority services running smoothly.
Message Creation Failure
- Check: Message creation failed.
- Recovery:
- If this is a temporary failure, retry at the application layer. For details, see RES09 Retries After Failures.
- If data still cannot be written after multiple retries, write the data to the local cache. After the service is available, write the data to the instance.
- If the connection to an overloaded instance failed, rectify the fault by referring to "Excessive CPU, Memory, or Bandwidth Usage."
Parent topic: DMS
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