Cross-AZ Deployment Check
Rule Details
Parameter |
Description |
---|---|
Rule Name |
gaussdb-mysql-instance-multiple-az-check |
Identifier |
gaussdb-mysql-instance-multiple-az-check |
Description |
If a TaurusDB instance is deployed in an AZ, this instance is non-compliant. |
Tag |
taurusdb |
Trigger Type |
Configuration change |
Filter Type |
gaussdbformysql.instance |
Rule Parameters |
None |
Application Scenarios
An AZ is a physical location that uses independent power supply and networks. AZs in the same region can communicate with each other over an intranet.
If your workloads require cross-AZ DR or are insensitive to cross-AZ latency, you are advised to deploy the primary node and read replicas in different AZs to achieve higher availability and reliability.
Solution
When buying a TaurusDB instance, select multiple AZs.
Rule Logic
- If a TaurusDB instance is deployed in a single AZ, this instance is non-compliant.
- If a TaurusDB instance is deployed across AZs, this instance is compliant.
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