When you no longer need read/write splitting or a readable secondary node, you can disable this feature. Before proceeding, ensure this change will not impact your system's performance or availability.
Prerequisites
Read/write splitting is enabled for your instance. For more information, see Enable read/write splitting (read-only routing endpoint).
Notes
-
After you disable a unified or secondary node read-only routing endpoint, it becomes invalid and can no longer be used for application connections. However, the public and private endpoints of the instance itself remain unchanged.
-
Disabling a read-only routing endpoint causes a connection interruption for up to 30 seconds. To prevent service interruptions, perform this operation during off-peak hours and ensure your application has an automatic reconnection mechanism.
-
Each time you re-enable a unified or secondary node read-only routing endpoint, a new endpoint may be generated.
Procedure
Disable the unified read-only routing endpoint
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 navigation pane on the left, click Cluster Management.
-
In the Read-only Network Information section, click Disable Readonly Splitting Address.
-
In the confirmation dialog box that appears, click OK.
Disable the secondary node read-only routing endpoint
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 navigation pane on the left, click Cluster Management.
-
In the Basic Information section, click Disable Read-only Routing Endpoint.
-
In the confirmation dialog box that appears, click OK.
Related topics
To re-enable read/write splitting or the secondary node read-only routing endpoint, see Enable read/write splitting (read-only routing endpoint).