What Do I Do If Replay Speed of Standby Nodes Cannot Catch Up with Write Speed of Primary Nodes?
Symptom
When workloads on a DB instance are heavy, the playback speed of standby nodes cannot catch up with write speed of primary nodes. After the system runs for a long time, logs are accumulated on the standby nodes. If a primary node is faulty, data restoration takes a long time and the database is unavailable, severely affecting system availability.
Solution
GaussDB provides ultimate RTO to minimize the data recovery time after a primary node is faulty and improve availability.
To use ultimate RTO, submit an application by choosing Service Tickets > Create Service Ticket in the upper right corner of the console.
Precautions
- Ultimate RTO focuses only on whether the RTO of standby nodes meets the requirements.
- Enabling ultimate RTO consumes CPU and memory resources of standby nodes.
- In 1.4 and earlier versions, flow control takes effect when ultimate RTO is enabled.
- Standby nodes do not support read operations after ultimate RTO is enabled. If you send read requests to a standby node, the standby node may fail to return the results.
Database Usage FAQs
- How Do I Use DAS to Query SQL Statements?
- What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Excel File?
- What Should I Do If My root Account Was Deleted by Mistake?
- What Do I Do If a DB Instance Is Locked?
- What Do I Do If Replay Speed of Standby Nodes Cannot Catch Up with Write Speed of Primary Nodes?
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.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore