Migrating MySQL® cluster hosts to a different availability zone

Written by

Updated at December 4, 2024

Managed Service for MySQL® cluster hosts reside in availability zones Yandex Cloud. To move hosts from one availability zone to another:

Create a subnet in the availability zone you want to move your hosts to.
Add a host to your cluster:
Management console

CLI

Terraform

REST API

gRPC API
1. Go to the folder page and select Managed Service for MySQL.
2. Click the cluster name and go to the Hosts tab.
3. Click Create host.
4. Specify the host parameters:
  - Availability zone to which you want to move the hosts.
  - New subnet.
  - Select Public access if the host must be accessible from outside Yandex Cloud.
5. Click Save.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

Run this command:
```
yc managed-mysql host add \
   --cluster-name <cluster_name> \
   --host zone-id=<availability_zone>,`
         `subnet-id=<new_subnet_ID>,`
         `assign-public-ip=<public_access_to_host:_true_or_false>
```
You can retrieve the cluster name with a list of clusters in the folder. In the zone-id parameter, specify the availability zone you are moving the hosts to.
1. Add a host manifest to the Terraform configuration file with the infrastructure plan:
  resource "yandex_mdb_mysql_cluster" "<cluster_name>" { ... host { zone = "<availability_zone>" subnet_id = "<new_subnet_ID>" assign_public_ip = <public_access_to_host:_true_or_false> } }
  In the zone parameter, specify the availability zone you are moving the hosts to.
2. Make sure the settings are correct.
  1. Using the command line, navigate to the folder that contains the up-to-date Terraform configuration files with an infrastructure plan.
  2. Run the command:
    
    terraform validate
    
    If there are errors in the configuration files, Terraform will point to them.
3. Confirm updating the resources.
  1. Run the command to view planned changes:
    
    terraform plan
    
    If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.
  2. If you are happy with the planned changes, apply them:
    
    Run the command:
    
    terraform apply
    
    Confirm the update of resources.
    
    Wait for the operation to complete.
1. Get an IAM token for API authentication and put it into the environment variable:
  export IAM_TOKEN="<IAM_token>"
2. Use the Cluster.addHosts method and make a request, e.g., via cURL:
  curl \ --request POST \ --header "Authorization: Bearer $IAM_TOKEN" \ --header "Content-Type: application/json" \ --url 'https://mdb.api.cloud.yandex.net/managed-mysql/v1/clusters/<cluster_ID>/hosts:batchCreate' \ --data '{ "hostSpecs": [ { "zoneId": "<availability_zone>", "subnetId": "<new_subnet_ID>", "assignPublicIp": <public_access_to_host:_true_or_false> } ] }'
  You can request the cluster ID with the list of clusters in the folder.
3. View the server response to make sure the request was successful.
1. Get an IAM token for API authentication and put it into the environment variable:
  export IAM_TOKEN="<IAM_token>"
2. Clone the cloudapi repository:
  cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
  Below, we assume the repository contents are stored in the ~/cloudapi/ directory.
3. Use the ClusterService/AddHosts call and make a request, e.g., via gRPCurl:
  grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/mysql/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>", "host_specs": [ { "zone_id": "<availability_zone>", "subnet_id": "<new_subnet_ID>", "assign_public_ip": <public_access_to_host:_true_or_false> } ] }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.mysql.v1.ClusterService.AddHosts
  You can request the cluster ID with the list of clusters in the folder.
4. View the server response to make sure the request was successful.
To successfully connect to the database after the migration is complete, specify the new host's FQDN in your backend or client (for example, in the code or graphical IDE). Delete the original host's FQDN in the source availability zone.

To find out the FQDN, get a list of hosts in the cluster:
```
yc managed-mysql host list --cluster-name <cluster_name>
```
The FQDN is specified in the command output under NAME. You can also use a special FQDN for a connection.
Delete the hosts in the source availability zone:
Management console

CLI

Terraform

REST API

gRPC API
1. Go to the folder page and select Managed Service for MySQL.
2. Click the cluster name and open the Hosts tab.
3. Click in the host's row, select Delete, and confirm the deletion.
Run the following command for each host:
```
yc managed-mysql host delete <host_FQDN> --cluster-name <cluster_name>
```
1. In the Terraform configuration file with the infrastructure plan, remove the host sections with the source availability zone from the cluster description.
2. Make sure the settings are correct.
  1. Using the command line, navigate to the folder that contains the up-to-date Terraform configuration files with an infrastructure plan.
  2. Run the command:
    
    terraform validate
    
    If there are errors in the configuration files, Terraform will point to them.
3. Type yes and press Enter.
  1. Run the command to view planned changes:
    
    terraform plan
    
    If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.
  2. If you are happy with the planned changes, apply them:
    
    Run the command:
    
    terraform apply
    
    Confirm the update of resources.
    
    Wait for the operation to complete.
1. Use the Cluster.deleteHosts method and make a request, e.g., via cURL:
  curl \ --request POST \ --header "Authorization: Bearer $IAM_TOKEN" \ --header "Content-Type: application/json" \ --url 'https://mdb.api.cloud.yandex.net/managed-mysql/v1/clusters/<cluster_ID>/hosts:batchDelete' \ --data '{ "hostNames": [ "<host_FQDN>" ] }'
  Where hostNames is the array with the host to delete.
  
  You can provide only one host FQDN in a single request. If you need to delete multiple hosts, make a separate request for each of them.
2. View the server response to make sure the request was successful.
1. Use the ClusterService/DeleteHosts call and make a request, e.g., via gRPCurl:
  grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/mysql/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>", "host_names": [ "<host_FQDN>" ] }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.mysql.v1.ClusterService.DeleteHosts
  Where host_names is the array with the host to delete.
  
  You can provide only one host FQDN in a single request. If you need to delete multiple hosts, make a separate request for each of them.
2. View the server response to make sure the request was successful.
Wait until the cluster status changes to Alive. In the management console, go to the folder page and select Managed Service for MySQL. You can see the cluster status in the Availability column.

Note

Not available for clusters with hosts residing in the ru-central1-d availability zone:

Intel Broadwell platform
Local SSD storage if using Intel Cascade Lake

Specifics of migration in Yandex Data Transfer

If your cluster is used as an endpoint when transferring data with Data Transfer, and the transfer type is Replication or Snapshot and increment, restart the transfer after migrating the cluster. This way, the transfer will get data about the cluster's new topology.

You do not need to restart Snapshot transfers, as information about the new topology is provided automatically while activating them.

To restart a transfer, choose one of the two methods:

Deactivate the transfer and wait for its status to change to Stopped. Next, reactivate the transfer and wait for its status to change to Replicating.
Update any setting for the transfer or endpoint.

For more information, see Migrating a Data Transfer transfer and endpoints to a different availability zone.

Note

Enable GTID mode (GTID-MODE = ON) for your MySQL® cluster used as a source endpoint during a transfer.

Migrating MySQL® cluster hosts to a different availability zone

Specifics of migration in Yandex Data TransferSpecifics of migration in Yandex Data Transfer

Was the article helpful?

Specifics of migration in Yandex Data Transfer