Enabling and disabling high availability on an instance

This page describes how to configure an instance for high availability.

You can configure an instance for high availability when you create the instance, or you can enable high availability on an existing instance.

For more information about high availability, see Overview of the high availability configuration.

Creating a new instance configured for high availability

When you create an instance and configure it for high availability, Cloud SQL creates it as a regional instance.

To create an instance configured for high availability:

Console

  1. In the Google Cloud Console, go to the Cloud SQL Instances page.

    Go to Cloud SQL Instances

  2. Select Create instance.
  3. In the Choose region and zonal availability section, select Multiple zones (Highly available).
  4. Expand Specify zones.
  5. Select the region and the primary and secondary zones. The following conditions apply when the secondary zone is used during instance creation or edit:
    • The zones default to Any for the primary zone and Any (different from primary) for the secondary zone.
    • If both the primary and secondary zones are specified, they must be distinct zones.

  6. Click Save.

    You are returned to the instance page for the primary instance while the instance is updated.

gcloud

  1. Create the regional instance:
    gcloud sql instances create REGIONAL_INSTANCE_NAME \
    --availability-type=REGIONAL \
    --database-version=SQLSERVER_2017_STANDARD \
    --cpu=NUMBER_CPUS \
    --memory=MEMORY_SIZE
    
  2. Configure the root user:
    gcloud sql users set-password root no-host \
    --instance=REGIONAL_INSTANCE_NAME \
    --password=PASSWORD
    
For a complete list of available parameters, see the gcloud sql instances create reference page.

REST v1beta4

For the complete list of parameters for this request, see the instances:insert page.

Create the regional instance.

  1. Before using any of the request data below, make the following replacements:

    • project-id: The project ID
    • instance-name: The instance name
    • database-version: The database version enum string
    • region The GCP region
    • machine-type The machine type

    HTTP method and URL:

    POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances

    Request JSON body:

    {
      "name": "instance-name",
      "region": "region",
      "databaseVersion": "database-version",
       "settings": {
         "tier": "machine-type",
         "backupConfiguration": {
             "enabled": true
          },
          "availabilityType": "REGIONAL"
       }
    }
    

    To send your request, expand one of these options:

    You should receive a JSON response similar to the following:

  2. When the instance finishes initializing, update the root password on the instance:

    Before using any of the request data below, make the following replacements:

    • project-id: The project ID
    • instance-id: The instance ID
    • password: The new root user password

    HTTP method and URL:

    PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users?host=%25&name=sqlserver'

    Request JSON body:

    {
       "name": "sqlserver",
       "host": "nohost",
       "password": "password"}
    

    To send your request, expand one of these options:

    You should receive a successful status code (2xx) and an empty response.

For more details about creating an instance, see Creating Instances.

Configuring an existing instance for high availability

Configuring an existing instance for high availability causes a few minutes of downtime while the instance is reconfigured.

To configure an existing instance for high availability:

Console

  1. In the Google Cloud Console, go to the Cloud SQL Instances page.

    Go to Cloud SQL Instances

  2. Click the instance name to open its Overview page.
  3. Click Edit.
  4. In the Auto backups and high availability configuration option section, select High availability (regional). It's also recommended that you enable Automate backups.
  5. Click Save.

    You are returned to the instance page for the primary instance while the instance is updated.

gcloud

Update the instance to be regional:

gcloud sql instances patch INSTANCE_NAME \
--availability-type REGIONAL

For reference information, see gcloud sql instances patch.

REST v1beta4

Update the instance to be a regional instance:

Before using any of the request data below, make the following replacements:

  • project-id: The project ID
  • instance-name: The instance name

HTTP method and URL:

PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name

Request JSON body:

{
  "settings": {"availabilityType": "REGIONAL" }
}

To send your request, expand one of these options:

You should receive a successful status code (2xx) and an empty response.

Initiating failover

Testing failover is optional, but is recommended so that you can see how your application responds in the event of a failover.

To learn more about failovers, see the Failover overview.

gcloud

Initiate the failover:

gcloud sql instances failover PRIMARY_INSTANCE_NAME

REST v1beta4

  1. Describe the primary instance to get the value of the settingsVersion field.

    Before using any of the request data below, make the following replacements:

    • project-id: The project ID
    • instance-id: The instance ID

    HTTP method and URL:

    GET https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id

    To send your request, expand one of these options:

    You should receive a JSON response similar to the following:

    {
      "kind": "sql#instance",
      "state": "RUNNABLE",
      "databaseVersion": "MYSQL_5_7",
      "settings": {
        "authorizedGaeApplications": [],
        "tier": "db-f1-micro",
        "kind": "sql#settings",
        "pricingPlan": "PER_USE",
        "replicationType": "SYNCHRONOUS",
        "activationPolicy": "ALWAYS",
        "ipConfiguration": {
          "authorizedNetworks": [],
          "ipv4Enabled": true
        },
        "locationPreference": {
          "zone": "asia-east1-a",
          "kind": "sql#locationPreference"
        },
        "dataDiskType": "PD_SSD",
        "backupConfiguration": {
          "startTime": "08:00",
          "kind": "sql#backupConfiguration",
          "enabled": true,
          "binaryLogEnabled": true
        },
        "settingsVersion": "13",
        "storageAutoResizeLimit": "0",
        "storageAutoResize": true,
        "dataDiskSizeGb": "10"
      },
      "etag": "etag-id",
      "ipAddresses": [
        {
          "type": "PRIMARY",
          "ipAddress": "10.0.0.1"
        }
      ],
      "serverCaCert": {
        "kind": "sql#sslCert",
        "certSerialNumber": "0",
        "cert": "certificate-id",
        "commonName": "C=US,O=Google\\, Inc,CN=Google Cloud SQL Server CA,dnQualifier=dn-qualifier-id",
        "sha1Fingerprint": "sha-id",
        "instance": "instance-id",
        "createTime": "2019-06-28T22:46:35.052Z",
        "expirationTime": "2029-06-25T22:47:35.052Z"
      },
      "instanceType": "CLOUD_SQL_INSTANCE",
      "project": "project-id",
      "serviceAccountEmailAddress": "service-acct-id@gcp-sa-cloud-sql.iam.gserviceaccount.com",
      "backendType": "SECOND_GEN",
      "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id",
      "connectionName": "project-id:region:instance-id",
      "name": "instance-id",
      "region": "asia-east1",
      "gceZone": "asia-east1-a"
    }
    
  2. Initiate the failover:

    Before using any of the request data below, make the following replacements:

    • project-id: The project ID
    • instance-name: The instance name
    • settings-version: The settingsVersion from instanceInfo

    HTTP method and URL:

    POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name/failover

    Request JSON body:

    {
      "failoverContext":
         {
            "settingsVersion":"settings-version"
         }
    }
    

    To send your request, expand one of these options:

    You should receive a JSON response similar to the following:

The instance fails over and is not available to serve data for a few minutes.

Verifying an instance has high availability

To verify an instance has high availability:

Console

  1. In the Google Cloud Console, go to the Cloud SQL Instances page.

    Go to Cloud SQL Instances

  2. Click the instance name to open its Overview page.
  3. In the Configuration section, it shows Highly available (regional).

gcloud

gcloud sql instances describe INSTANCE_NAME
The output indicates availabilityType is REGIONAL.

REST v1beta4

Before using any of the request data below, make the following replacements:

  • project-id: The project ID
  • instance-id: The instance ID

HTTP method and URL:

GET https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id

To send your request, expand one of these options:

You should receive a JSON response similar to the following:

{
  "kind": "sql#instance",
  "state": "RUNNABLE",
  "databaseVersion": "SQLSERVER_2017_STANDARD",
  "settings": {
    "authorizedGaeApplications": [],
    "tier": "db-f1-micro",
    "kind": "sql#settings",
    "pricingPlan": "PER_USE",
    "replicationType": "SYNCHRONOUS",
    "activationPolicy": "ALWAYS",
    "ipConfiguration": {
      "authorizedNetworks": [],
      "ipv4Enabled": true
    },
    "locationPreference": {
      "zone": "asia-east1-a",
      "kind": "sql#locationPreference"
    },
    "dataDiskType": "PD_SSD",
    "backupConfiguration": {
      "startTime": "08:00",
      "kind": "sql#backupConfiguration",
      "enabled": true,
    },
    "settingsVersion": "13",
    "storageAutoResizeLimit": "0",
    "storageAutoResize": true,
    "dataDiskSizeGb": "10"
  },
  "etag": "etag-id",
  "ipAddresses": [
    {
      "type": "PRIMARY",
      "ipAddress": "10.0.0.1"
    }
  ],
  "serverCaCert": {
    "kind": "sql#sslCert",
    "certSerialNumber": "0",
    "cert": "certificate-id",
    "commonName": "C=US,O=Google\\, Inc,CN=Google Cloud SQL Server CA,dnQualifier=dn-qualifier-id",
    "sha1Fingerprint": "sha-id",
    "instance": "instance-id",
    "createTime": "2019-06-28T22:46:35.052Z",
    "expirationTime": "2029-06-25T22:47:35.052Z"
  },
  "instanceType": "CLOUD_SQL_INSTANCE",
  "project": "project-id",
  "serviceAccountEmailAddress": "service-acct-id@gcp-sa-cloud-sql.iam.gserviceaccount.com",
  "backendType": "SECOND_GEN",
  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id",
  "connectionName": "project-id:region:instance-id",
  "name": "instance-id",
  "region": "asia-east1",
  "gceZone": "asia-east1-a"
}

The output indicates availabilityType is REGIONAL.

Disabling high availability on an instance

Before you perform this procedure, make sure there are no operations currently running on the instance.

To disable high availability:

Console

  1. In the Google Cloud Console, go to the Cloud SQL Instances page.

    Go to Cloud SQL Instances

  2. Click the instance name to open its Overview page.
  3. Click Edit.
  4. Open Auto backups.
  5. In the Availabilitysection, click Single zone.
  6. Click Save. This edit requires a restart of the instance.
  7. When you see the message box, click Save and restart.

gcloud

For reference information, see gcloud sql instances patch.
gcloud sql instances patch INSTANCE_NAME \
--availability-type ZONAL

REST v1beta4

The following request uses the instances:patch method to change the availability type on the instance to ZONAL.

Before using any of the request data below, make the following replacements:

  • project-id: The project ID
  • instance-name: The instance name

HTTP method and URL:

PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name

Request JSON body:

{
  "settings": {"availabilityType": "ZONAL" }
}

To send your request, expand one of these options:

You should receive a successful status code (2xx) and an empty response.

Troubleshooting

Click the links in the table for details:

For this problem... The issue might be... Try this...
Can't find metrics for manual failover. Only automatic failovers go into the metrics. N/A
CPU and RAM are near 100% usage Instance machine size is too small for the load. Upgrade the instance machine size.

Can't find metrics for manual failover

You performed a manual failover and can't find a corresponding entry in Metrics Explorer in the automatic failover metrics.

The issue might be

Only automatic failovers go into the metrics. Manually initiated failovers do not.

Things to try

N/A


CPU and RAM are near 100% usage

Cloud SQL instance resources (CPU and RAM) are near 100% usage, causing the high availability instance to go down.

The issue might be

The instance machine size is too small for the load.

Things to try

Edit the instance to upgrade to a larger machine size to get more CPUs and memory.

What's next