All Products
Search
Document Center

AnalyticDB for MySQL:Change the VPC and vSwitch for a cluster

Last Updated:Apr 15, 2024

If you want to connect an AnalyticDB for MySQL cluster with an Elastic Compute Service (ECS) instance that is not located in the same virtual private cloud (VPC) over an internal network, you can change the VPC for the AnalyticDB for MySQL cluster.

Usage notes

  • Changing the VPC and vSwitch for an AnalyticDB for MySQL cluster is an asynchronous operation. During the change process, you may encounter transient connections and read and write failures. We recommend that you perform the change operation during off-peak hours and make sure that your application is configured to automatically reconnect to the cluster.

  • Changing the VPC and vSwitch for an AnalyticDB for MySQL cluster may result in a virtual IP address (VIP) change. We recommend that you use the VPC endpoint of the cluster to connect to the cluster. The endpoint does not change. Example: am-bp13er819d288****90650.ads.aliyuncs.com.

    After the change operation is complete, the Domain Name Server (DNS) cache that is stored on your computer is refreshed and you may fail to connect to the cluster for several minutes.

  • After you change the VPC and vSwitch for an AnalyticDB for MySQL cluster, the IP address whitelists are not automatically updated. If the CIDR block of the cluster changes, the IP address whitelists may become invalid. In this case, you must reconfigure the IP address whitelists.

  • After you change the VPC and vSwitch for an AnalyticDB for MySQL cluster that has the Elastic Network Interface (ENI) feature enabled, the ENI that is used is not automatically switched to the new VPC or vSwitch. If you want to switch the ENI to the new VPC or vSwitch, disable the ENI feature and then re-enable the ENI feature.

  • After you change the VPC and vSwitch for an AnalyticDB for MySQL Data Lakehouse Edition (V3.0) cluster or an AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster in elastic mode, you can delete the original VPC and vSwitch. After you change the VPC and vSwitch for an AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster in reserved mode, you cannot delete the original VPC and vSwitch. This is because specific underlying applications are deployed in the original VPC and vSwitch.

  • After you change the VPC and vSwitch for an AnalyticDB for MySQL Data Lakehouse Edition (3.0) cluster, the notebook that is used is not automatically switched to the new VPC and vSwitch. If you want to switch the notebook to the new VPC and vSwitch, restart the notebook.

Procedure

  1. Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that you want to manage and click the cluster ID.

  2. In the Network Information section, click Change VPC and vSwitch to the right of the VPC ID.

  3. In the Change VPC and vSwitch dialog box, select a VPC and a vSwitch.

    Note

    If no options are displayed, the region does not contain other VPCs or vSwitches. In this case, you can create a VPC and a vSwitch. For more information, see Create and manage a VPC.

  4. Click OK.

    Note

    When the VPC and vSwitch are being changed, the cluster status changes to Modifying Network Address. When the cluster status changes to Running, the change operation is complete.