Stay organized with collections
Save and categorize content based on your preferences.
Partially updates a cluster within a project. This method is the preferred way to update a Cluster.
To enable and update autoscaling, set clusterConfig.cluster_autoscaling_config. When autoscaling is enabled, serveNodes is treated as an OUTPUT_ONLY field, meaning that updates to it are ignored. Note that an update cannot simultaneously set serveNodes to non-zero and clusterConfig.cluster_autoscaling_config to non-empty, and also specify both in the updateMask.
To disable autoscaling, clear clusterConfig.cluster_autoscaling_config, and explicitly set a serve_node count via the updateMask.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-08 UTC."],[[["\u003cp\u003eThis method updates a cluster within a project and is the recommended approach for cluster updates.\u003c/p\u003e\n"],["\u003cp\u003eAutoscaling can be enabled by configuring \u003ccode\u003eclusterConfig.cluster_autoscaling_config\u003c/code\u003e, which will make \u003ccode\u003eserveNodes\u003c/code\u003e an output-only field.\u003c/p\u003e\n"],["\u003cp\u003eDisabling autoscaling involves clearing \u003ccode\u003eclusterConfig.cluster_autoscaling_config\u003c/code\u003e and explicitly setting the \u003ccode\u003eserve_node\u003c/code\u003e count via the \u003ccode\u003eupdateMask\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe HTTP request for this update is a PATCH request to a specific URL, and it requires specifying the cluster's unique name and the \u003ccode\u003eupdateMask\u003c/code\u003e in the parameters.\u003c/p\u003e\n"],["\u003cp\u003eThe request requires one of a list of OAuth scopes for authorization.\u003c/p\u003e\n"]]],[],null,["# Method: projects.instances.clusters.partialUpdateCluster\n\nPartially updates a cluster within a project. This method is the preferred way to update a Cluster.\n\nTo enable and update autoscaling, set clusterConfig.cluster_autoscaling_config. When autoscaling is enabled, serveNodes is treated as an OUTPUT_ONLY field, meaning that updates to it are ignored. Note that an update cannot simultaneously set serveNodes to non-zero and clusterConfig.cluster_autoscaling_config to non-empty, and also specify both in the updateMask.\n\nTo disable autoscaling, clear clusterConfig.cluster_autoscaling_config, and explicitly set a serve_node count via the updateMask.\n\n### HTTP request\n\n`PATCH https://bigtableadmin.googleapis.com/v2/{cluster.name=projects/*/instances/*/clusters/*}`\n\nThe URL uses [gRPC Transcoding](https://google.aip.dev/127) syntax.\n\n### Path parameters\n\n### Query parameters\n\n### Request body\n\nThe request body contains an instance of [Cluster](/bigtable/docs/reference/admin/rest/v2/projects.instances.clusters#Cluster).\n\n### Response body\n\nIf successful, the response body contains an instance of [Operation](/bigtable/docs/reference/admin/rest/v2/operations#Operation).\n\n### Authorization scopes\n\nRequires one of the following OAuth scopes:\n\n- `https://www.googleapis.com/auth/bigtable.admin`\n- `https://www.googleapis.com/auth/bigtable.admin.cluster`\n- `https://www.googleapis.com/auth/bigtable.admin.instance`\n- `https://www.googleapis.com/auth/cloud-bigtable.admin`\n- `https://www.googleapis.com/auth/cloud-bigtable.admin.cluster`\n- `https://www.googleapis.com/auth/cloud-platform`\n\nFor more information, see the [Authentication Overview](/docs/authentication#authorization-gcp)."]]
