[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[],[],null,["# Start, stop, or restart instances\n\nThis page describes how to start, stop, or restart the primary instance and a read pool instance. You can also restart a secondary instance and a node in a read pool of an AlloyDB cluster.\n\nThe start, stop, or restart operations don't change the inbound public IP or the Private Services Connect URI of the instance.\n\nBefore you begin\n----------------\n\n- The Google Cloud project you are using must be enabled to access AlloyDB.\n\n- You must have one of the following IAM roles in the Google Cloud project you are using:\n\n - (`roles/alloydb.admin`) (the AlloyDB Admin predefined IAM role)\n - (`roles/owner`) (the Owner basic IAM role)\n - (`roles/editor`) (the Editor basic IAM role)\n\n If you don't have any of these roles, contact your Organization Administrator to request access.\n- The AlloyDB cluster is in `READY` state.\n\nActivation policy\n-----------------\n\nWhen you start or stop instance, the activation policy must be set to indicate the operation you are performing. The activation policy indicates if the instance is activated to accept connection requests.\n\nActivation policy options are:\n\n- `ALWAYS` - The instance is always up and running.\n- `NEVER`- The instance is inactive and isn't accepting connections.\n\nTo start your instance, set your activation policy to `ALWAYS`. To stop your instance and avoid instance charges, set your activation policy to `NEVER`.\n\nStop an instance\n----------------\n\nYou can manually stop a primary or read pool instance when needed. When you stop an instance, it remains stopped, and doesn't respond to application connections, until you start it again. You can't stop a secondary instance.\n\nStopping an instance temporarily halts automatic updates. The data stored in the cluster is unaffected and any backup configuration for the cluster remains active.\n\nStopped instances don't incur any compute charges associated with the instance. If public IP is enabled on the instance, then you incur idle static external IP charges.\n| **Note:** Before stopping the primary instance, you must stop any active read pool instances or cross region replication (CRR) clusters (secondary clusters). For CRR (secondary) clusters, ensure that you either promote or delete the CRR (secondary) cluster before stopping the primary instance. To stop an active read pool instance ensure that the primary instance is in `READY` state.\n\nTo stop an instance: \n\n### Console\n\n1. In the Google Cloud console, go to the **Clusters** page.\n\n [Go to Clusters](https://console.cloud.google.com/alloydb/clusters)\n2. Click a cluster in the **Resource Name** column.\n\n3. In the **Overview** page that opens, go to the **Instances in your\n cluster** section and view the details about your instance.\n\n4. In **Stop database instance?** , click **Stop**.\n\nThe activation policy of the instance is set to `NEVER` and the instance is stopped.\n\n### gcloud\n\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\n\u003cbr /\u003e\n\nUse the [`gcloud alloydb instances update`](/sdk/gcloud/reference/beta/alloydb/instances/update) command to stop an instance. \n\n gcloud alloydb instances update \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e \\\n --cluster=\u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e \\\n --activation-policy=NEVER\n ```\n Replace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: The ID of the instance.\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: The instance's region ID.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: The ID of the instance's cluster.\n\nStart an instance\n-----------------\n\nWhen you start the instance, AlloyDB applies the latest minor version for the database. As starting an instance isn't a maintenance activity, any maintenance deny periods configured for the instance are ignored.\n\nTo start a stopped instance: \n\n### Console\n\n1. In the Google Cloud console, go to the **Clusters** page.\n\n [Go to Clusters](https://console.cloud.google.com/alloydb/clusters)\n2. Click a cluster in the **Resource Name** column.\n\n3. In the **Overview** page that opens, go to the **Instances in your\n cluster** section and view the details about your instance.\n\n4. In **Start database instance?** , click **Start**.\n\nThe activation policy of the instance is set to `ALWAYS` and the instance is started.\n\n### gcloud\n\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\n\u003cbr /\u003e\n\nUse the [`gcloud alloydb instances update`](/sdk/gcloud/reference/beta/alloydb/instances/update) command to start an instance. \n\n gcloud alloydb instances update \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e \\\n --cluster=\u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e \\\n --activation-policy=ALWAYS\n ```\n Replace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: The ID of the instance.\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: The instance's region ID.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: The ID of the instance's cluster.\n\nRestart an instance\n-------------------\n\nWhen you initiate a restart of an instance, it disrupts all connections that are available on the instance. After the instance restarts, and it's ready to accept new connections.\nRestarting an instance doesn't change the private IP address of the instance.\n\n### Restart a primary,secondary, or read pool instance\n\n### Console\n\n1. In the Google Cloud console, go to the **Clusters** page.\n\n [Go to Clusters](https://console.cloud.google.com/alloydb/clusters)\n2. Click a cluster in the **Resource Name** column.\n3. In the **Overview** page, go to the **Instances in your cluster** section, choose the primary or a read pool instance, and click **Restart**.\n\n### gcloud\n\nTo use the gcloud CLI, you can\n[install and initialize](/sdk/docs/install) the Google Cloud CLI, or you\ncan use [Cloud Shell](/shell/docs/using-cloud-shell).\n\nRestart the instance: \n\n```\ngcloud alloydb instances restart INSTANCE_ID \\\n --cluster=CLUSTER_ID \\\n --region=REGION_ID \\\n --project=PROJECT_ID \\\n [--async]\n \n```\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: the ID of the instance.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: the ID of the cluster where the instance is available.\n- \u003cvar translate=\"no\"\u003eREGION_ID\u003c/var\u003e: the region where the instance is placed.\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project where the cluster is placed.\n- `async`: an optional flag to return immediately, without waiting for the operation in progress to complete.\n\n### Restart specific nodes of a read pool\n\nYou can use the gcloud CLI to restart one or more nodes of a\nread pool.\n\nThe following command shows how you can restart a node of a read pool: \n\n```\ngcloud alloydb instances restart INSTANCE_ID \\\n --cluster=CLUSTER_ID \\\n --region=REGION_ID \\\n --node-ids=NODE_ID \\\n \n```\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: the ID of the readpool instance.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: the ID of the cluster where the instance is available.\n- \u003cvar translate=\"no\"\u003eNODE_ID\u003c/var\u003e: the [ID of the node](/alloydb/docs/troubleshoot/read-pools#list-nodes) that needs a restart, for example-`j71a-read-pool-054b8861-2ln8`.\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project where the cluster is placed.\n- `--async`: an optional flag to return immediately, without waiting for the operation in progress to complete.\n\nThe following example shows how you can restart multiple nodes: \n\n```\ngcloud alloydb instances restart INSTANCE_ID \\\n --cluster=CLUSTER_ID \\\n --region=REGION_ID \\\n --node-ids=NODE_ID1,NODE_ID2 \\\n \n```\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_ID\u003c/var\u003e: the ID of the readpool instance.\n- \u003cvar translate=\"no\"\u003eCLUSTER_ID\u003c/var\u003e: the ID of the cluster where the instance is available.\n- \u003cvar translate=\"no\"\u003eNODE_ID1,NODE_ID2\u003c/var\u003e: the list of nodes that need a restart.\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project where the cluster is placed.\n- `--async`: an optional flag to return immediately, without waiting for the operation in progress to complete.\n\nWhat's next\n-----------\n\n- Learn about [creating a primary instance](/alloydb/docs/instance-primary-create)\n- Update [Cluster and instance settings](/alloydb/docs/cluster-settings)"]]
