This document describes how to switch the instance deployment mode between single-AZ and multi-AZ in the TDSQL-C for MySQL console.
Note：
The term "AZ" in this article refers to Availability Zone.
Upgrading from Single-AZ to Multi-AZ
On the cluster list page, proceed according to the actually used view mode:
Tab View
List view
1. Log in to the TDSQL-C for MySQL console, locate the cluster list on the left, and click the target cluster to enter the cluster management page.
2. On the cluster management page, click
next to Deployment Mode.
3. In the pop-up window, select Yes for Multi-AZ Deployment, select a secondary availability zone and binlog replication method, and click OK.
Parameter
Description
Multi-AZ Deployment
Selecting Yes indicates changing the cluster deployment mode from single-AZ deployment to multi-AZ deployment.
Secondary AZ
Select the availability zone of the secondary database. The actual availability zones supported for selection depend on the Modify Deployment Mode window.
Binlog Replication Method
Select the binlog replication method. The default is Async replication. Async, Semi-sync, and Strong sync replication modes are supported.
Note:
Note that Strong sync replication can impact the instance performance.
4. When the cluster status becomes Running, the primary and secondary availability zone information can be viewed in the architecture diagram under the cluster details.
1. Log in to the TDSQL-C for MySQL console and click a cluster name in the cluster list or Manage in the Operation column to enter the cluster details page.
2. In the Availability Info module on the cluster details page, click Modify after Deployment Mode.
3. In the pop-up window, select Yes for Multi-AZ Deployment, select a secondary availability zone and binlog replication method, and click OK.
Parameter
Description
Multi-AZ Deployment
Selecting Yes indicates changing the cluster deployment mode from single-AZ deployment to multi-AZ deployment.
Secondary AZ
Select the availability zone of the secondary database. The actual availability zones supported for selection depend on the Modify Deployment Mode window
Binlog Replication Method
Select the binlog replication method. The default is Async replication. Async, Semi-sync, and Strong sync replication modes are supported.
Note:
Note that Strong sync replication can impact the instance performance.
4. When the cluster status becomes Running, you can view the information of the primary and secondary AZs on the cluster details page.
Downgrading from Multi-AZ to Single-AZ
On the cluster list page, proceed according to the actually used view mode:
Tab View
List view
1. Log in to the TDSQL-C for MySQL console, locate the cluster list on the left, and click the target cluster to enter the cluster management page.
2. On the cluster management page, click
next to Deployment Mode.
3. In the pop-up window, select No for Multi-AZ Deployment and click OK.
Note:
Only the secondary AZ can switch between single-AZ and multi-AZ deployment mode, but the primary AZ cannot.
1. Log in to the TDSQL-C for MySQL console, locate the cluster list, click a cluster ID or Operation column's Manage to enter the cluster details page.
2. In the Availability Info module on the cluster details page, click Modify after Deployment Mode.
3. In the pop-up window, select No for Multi-AZ Deployment and click OK.
Note:
Only the secondary AZ can switch between single-AZ and multi-AZ deployment mode, but the primary AZ cannot.
FAQs
Where can I query the AZ information of a cluster?
List View
In the AZ column in the cluster list.
In Basic Info > Region/AZ on the cluster details page.
In Availability Info on the cluster details page.
Tab View
The architecture diagram, which can be found under the Cluster Details section.
Will my cluster run normally during the AZ modification?
During the start and modification operations of the AZ modification task, normal access to read-only and read-write instances will be unaffected.
The database connection addresses (cluster’s read-write address and read-only address) will remain unchanged after the AZ is modified, so you can continue to access your cluster at these addresses.
