What Precautions Should Be Taken When Using DDS?
- Failover
DDS uses multiple mongos, replica sets, and shards to ensure data reliability. When a mongos is faulty, the other mongos takes over services immediately to ensure service continuity. A replica set contains multiple secondary nodes. When the primary node is faulty, DDS selects a secondary node as the new primary within 30 seconds.
- ECSs used for instances are invisible to you. Your applications can access only the IP addresses and ports corresponding to the database.
- Backup files stored on OBS are invisible to you. They are only visible in the DDS backend management system.
- With DDS, you do not need to perform basic database O&M operations, such as enabling HA and installing security patches, but you should still note:
- Whether the vCPUs, IOPS, and storage space for DDS DB instances are sufficient. If any of them is insufficient, optimize or upgrade the related configuration.
- Whether DDS DB instances have performance issues, whether there are a large number of slow queries, whether SQL statements need to be optimized, and whether there are redundant or missing indexes.
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.
Chatbot