Restart an instance

This page describes how to restart the primary instance or a read pool instance of an AlloyDB cluster.

When you initiate a restart of an instance, it disrupts all connections that are available on the instance, the instance restarts, and is ready to accept new connections.

Restarting an instance does not change the private IP address of the instance.

Before you begin

  • The Google Cloud project you are using must have been enabled to access AlloyDB.
  • You must have one of these IAM roles in the Google Cloud project you are using:
    • roles/alloydb.admin (the AlloyDB Admin predefined IAM role)
    • roles/owner (the Owner basic IAM role)
    • roles/editor (the Editor basic IAM role)

    If you don't have any of these roles, contact your Organization Administrator to request access.

Procedure

Console

  1. In the Google Cloud console, go to the Clusters page.

    Go to Clusters

  2. Click a cluster in the Resource Name column.
  3. In the Overview page, go to the Instances in your cluster section, choose the primary or a read pool instance, and click Restart.

gcloud

To use the gcloud CLI, you can install and initialize the Google Cloud CLI, or you can use Cloud Shell.

Restart the instance:

gcloud alloydb instances restart INSTANCE_ID \
    --cluster=CLUSTER_ID \
    --region=REGION_ID \
    --project=PROJECT_ID \
    [--async]
  • INSTANCE_ID: The ID of the instance.
  • CLUSTER_ID: The ID of the cluster where the instance is available.
  • REGION_ID: The region where the instance is placed.
  • PROJECT_ID: The ID of the project where the cluster is placed.
  • --async: An optional flag to return immediately, without waiting for the operation in progress to complete.