If your ApsaraDB RDS for SQL Server instance no longer requires read/write splitting, you can disable read/write splitting for your RDS instance. Before you disable read/write splitting, we recommend that you evaluate your business requirements and ensure that disabling read/write splitting does not affect the performance and availability of the RDS instance.
Prerequisites
Read/write splitting is enabled for the RDS instance. For more information, see Enable read/write splitting by enabling the read-only routing endpoint.
Usage notes
After you disable read/write splitting by disabling the read-only routing endpoint, your application can no longer connect to the read-only RDS instance by using the read-only routing endpoint. However, the endpoints of the primary and read-only instances remain unchanged. If you enable read/write splitting again, the read-only routing endpoint may change.
When you disable the read-only routing endpoint for your RDS instance, a transient connection that lasts 30 seconds or less occurs. We recommend that you disable the read-only routing endpoint during off-peak hours. Make sure that your application is configured to automatically reconnect to the RDS instance. This prevents interruptions to your workloads.
After you disable the read-only routing endpoint, it becomes invalid. Before you disable the read-only routing endpoint, make sure that your application no longer uses this endpoint.
Procedure
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the instance ID.
In the left-side navigation pane, click Cluster Management to view the read-only routing endpoint and port.
In the Basic Information section, click Disable Read-only Routing Endpoint.
In the message that appears, click OK.
References
If you want to enable read/write splitting again, perform the operations provided in Enable read/write splitting by enabling the read-only routing endpoint.