12.3.2 Disabling High Availability on a DB System

When disabling high availability on a DB system, the primary instance located in the preferred primary placement is converted to a standalone DB system and the two secondary instances are deleted.

This task requires the following:

• A running DB system with high availability enabled.
• The DB System has no PrivateLinks attached to. If it has any, delete them from the DB System. Once the operation for disabling high availability is completed, recreate the PrivateLinks for the standalone DB System.

To disable high availability for a DB system, do the following:

1. In the HeatWave Console, select the Resources tab.
2. On the DB Systems tab, in the list of DB Systems, find the DB System for which you want to disable high availability, and do one of the following:
   1. Click the row of the DB System to highlight it, and then select from the Actions menu Disable High Availability.
   2. Click the name of the DB System to open the MySQL DB System Details page for the selected DB System, and then click the Disable High Availability button.
3. In the Disable High Availability dialog box, click Disable to confirm that you are disabling high availability, or click Cancel.

The DB system enters the UPDATING state. If the primary instance is running in the preferred primary placement, no downtime occurs. If the primary instance is not running in the preferred primary placement, a failover occurs and this causes a short downtime.

Note:

You can avoid the downtime by changing the preferred primary placement of the DB system to the current primary instance by performing a Switchover before disabling high availability.

If the updating process fails, the DB system returns to a high availability state. To view the reasons for the failure, navigate to the Service Events pane (see Events) and check the event details.