Evaluates whether each ApsaraDB RDS instance uses a non-asynchronous data replication mode. Asynchronous replication may cause data inconsistency between primary and secondary nodes. Semi-synchronous or synchronous mode is recommended.
Scenarios
Asynchronous replication offers better performance but may cause data inconsistency between primary and secondary instances. Synchronous replication ensures data consistency and provides high availability and disaster recovery.
Risk level
Default risk level: medium.
You can change the risk level based on your business requirements when you apply this rule.
Compliance evaluation logic
-
If the data replication mode of each ApsaraDB RDS instance is non-asynchronous, the evaluation result is Compliant.
-
If the data replication mode of an ApsaraDB RDS instance is asynchronous, the evaluation result is Non-compliant.
-
If ApsaraDB RDS instances are ApsaraDB RDS for MySQL Basic Edition instances or non-MySQL instances, the evaluation result is Not Applicable.
Rule details
|
Item |
Description |
|
Rule name |
rds-instance-sync-mode-check |
|
Rule ID |
|
|
Tag |
RDS and Instance |
|
Automatic remediation |
Not supported |
|
Trigger type |
Periodic execution |
|
Evaluation frequency |
Every 24 hours |
|
Supported resource type |
ApsaraDB RDS instance |
|
Input parameter |
None |
Non-compliance remediation
Set the data replication mode of each ApsaraDB RDS instance to non-asynchronous. For more information, see Query and change the data replication mode.