gcloud beta alloydb instances failover Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud beta alloydb instances failover - failover an AlloyDB instance within a given cluster
- SYNOPSIS
gcloud beta alloydb instances failoverINSTANCE--cluster=CLUSTER--region=REGION[--async][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(BETA)Failover an AlloyDB instance within a given cluster.- EXAMPLES
- To failover an instance, run:
gcloudbetaalloydbinstancesfailovermy-instance--cluster=my-cluster--region=us-central1 - POSITIONAL ARGUMENTS
INSTANCE- AlloyDB instance ID
- REQUIRED FLAGS
--cluster=CLUSTER- AlloyDB cluster ID
--region=REGION- Regional location (e.g.
asia-east1,us-east1). See thefull list of regions athttps://cloud.google.com/sql/docs/instance-locations.
- OPTIONAL FLAGS
--async- Return immediately, without waiting for the operation in progress to complete.
- GCLOUD WIDE FLAGS
- These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$gcloud helpfor details. - NOTES
- This command is currently in beta and might change without notice. Thesevariants are also available:
gcloudalloydbinstancesfailovergcloudalphaalloydbinstancesfailover
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-07 UTC.