If the endpoint of the PolarDB cluster is in read/write splitting mode, the evaluation result is Compliant.
Scenarios
Cluster endpoints in read/write splitting mode can significantly reduce latencies and enhance processing performance.
Risk level
Default risk level: high.
When you apply this rule, you can change the risk level based on your business requirements.
Compliance evaluation logic
- If the endpoint of the PolarDB cluster is in read/write splitting mode, the evaluation result is Compliant.
- If the endpoint of the PolarDB cluster is not in read/write splitting mode, the evaluation result is Incompliant. For more information about how to remediate an incompliant configuration, see the "Incompliance remediation" section of this topic.
Rule details
| Parameter | Description |
|---|---|
| Rule name | polardb-cluster-address-read-write-enabled |
| Rule identifier | polardb-cluster-address-read-write-enabled |
| Tag | PolarDB |
| Automatic remediation | Not supported |
| Trigger type | Periodic execution |
| Evaluation frequency | Interval of 24 hours |
| Supported resource type | PolarDB cluster |
| Input parameter | None |
Incompliance remediation
Set the endpoint of the PolarDB cluster to read/write splitting mode. For more information, see Configure Polar Proxy.