Reference documentation and code samples for the Cloud Bigtable V2 Client class AutoscalingTargets.
The Autoscaling targets for a Cluster. These determine the recommended nodes.
Generated from protobuf message google.bigtable.admin.v2.AutoscalingTargets
Namespace
Google \ Cloud \ Bigtable \ Admin \ V2
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ cpu_utilization_percent
int
The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80, otherwise it will return INVALID_ARGUMENT error.
↳ storage_utilization_gib_per_node
int
The storage utilization that the Autoscaler should be trying to achieve. This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster, otherwise it will return INVALID_ARGUMENT error. If this value is set to 0, it will be treated as if it were set to the default value: 2560 for SSD, 8192 for HDD.
getCpuUtilizationPercent
The cpu utilization that the Autoscaler should be trying to achieve.
This number is on a scale from 0 (no utilization) to
100 (total utilization), and is limited between 10 and 80, otherwise it
will return INVALID_ARGUMENT error.
Returns
Type
Description
int
setCpuUtilizationPercent
The cpu utilization that the Autoscaler should be trying to achieve.
This number is on a scale from 0 (no utilization) to
100 (total utilization), and is limited between 10 and 80, otherwise it
will return INVALID_ARGUMENT error.
Parameter
Name
Description
var
int
Returns
Type
Description
$this
getStorageUtilizationGibPerNode
The storage utilization that the Autoscaler should be trying to achieve.
This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD
cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster,
otherwise it will return INVALID_ARGUMENT error. If this value is set to 0,
it will be treated as if it were set to the default value: 2560 for SSD,
8192 for HDD.
Returns
Type
Description
int
setStorageUtilizationGibPerNode
The storage utilization that the Autoscaler should be trying to achieve.
This number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD
cluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster,
otherwise it will return INVALID_ARGUMENT error. If this value is set to 0,
it will be treated as if it were set to the default value: 2560 for SSD,
8192 for HDD.
[[["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-08-28 UTC."],[],[],null,["# Cloud Bigtable V2 Client - Class AutoscalingTargets (2.17.1)\n\nVersion latestkeyboard_arrow_down\n\n- [2.17.1 (latest)](/php/docs/reference/cloud-bigtable/latest/Admin.V2.AutoscalingTargets)\n- [2.17.0](/php/docs/reference/cloud-bigtable/2.17.0/Admin.V2.AutoscalingTargets)\n- [2.16.0](/php/docs/reference/cloud-bigtable/2.16.0/Admin.V2.AutoscalingTargets)\n- [2.15.0](/php/docs/reference/cloud-bigtable/2.15.0/Admin.V2.AutoscalingTargets)\n- [2.14.0](/php/docs/reference/cloud-bigtable/2.14.0/Admin.V2.AutoscalingTargets)\n- [2.13.0](/php/docs/reference/cloud-bigtable/2.13.0/Admin.V2.AutoscalingTargets)\n- [2.12.0](/php/docs/reference/cloud-bigtable/2.12.0/Admin.V2.AutoscalingTargets)\n- [2.11.1](/php/docs/reference/cloud-bigtable/2.11.1/Admin.V2.AutoscalingTargets)\n- [2.9.1](/php/docs/reference/cloud-bigtable/2.9.1/Admin.V2.AutoscalingTargets)\n- [2.8.0](/php/docs/reference/cloud-bigtable/2.8.0/Admin.V2.AutoscalingTargets)\n- [2.7.0](/php/docs/reference/cloud-bigtable/2.7.0/Admin.V2.AutoscalingTargets)\n- [2.6.3](/php/docs/reference/cloud-bigtable/2.6.3/Admin.V2.AutoscalingTargets)\n- [2.5.0](/php/docs/reference/cloud-bigtable/2.5.0/Admin.V2.AutoscalingTargets)\n- [2.4.0](/php/docs/reference/cloud-bigtable/2.4.0/Admin.V2.AutoscalingTargets)\n- [2.3.0](/php/docs/reference/cloud-bigtable/2.3.0/Admin.V2.AutoscalingTargets)\n- [2.2.1](/php/docs/reference/cloud-bigtable/2.2.1/Admin.V2.AutoscalingTargets)\n- [2.1.0](/php/docs/reference/cloud-bigtable/2.1.0/Admin.V2.AutoscalingTargets)\n- [2.0.1](/php/docs/reference/cloud-bigtable/2.0.1/Admin.V2.AutoscalingTargets)\n- [1.32.1](/php/docs/reference/cloud-bigtable/1.32.1/Admin.V2.AutoscalingTargets)\n- [1.31.1](/php/docs/reference/cloud-bigtable/1.31.1/Admin.V2.AutoscalingTargets)\n- [1.30.0](/php/docs/reference/cloud-bigtable/1.30.0/Admin.V2.AutoscalingTargets)\n- [1.29.2](/php/docs/reference/cloud-bigtable/1.29.2/Admin.V2.AutoscalingTargets)\n- [1.28.3](/php/docs/reference/cloud-bigtable/1.28.3/Admin.V2.AutoscalingTargets)\n- [1.27.0](/php/docs/reference/cloud-bigtable/1.27.0/Admin.V2.AutoscalingTargets)\n- [1.26.2](/php/docs/reference/cloud-bigtable/1.26.2/Admin.V2.AutoscalingTargets)\n- [1.25.0](/php/docs/reference/cloud-bigtable/1.25.0/Admin.V2.AutoscalingTargets)\n- [1.24.1](/php/docs/reference/cloud-bigtable/1.24.1/Admin.V2.AutoscalingTargets)\n- [1.23.0](/php/docs/reference/cloud-bigtable/1.23.0/Admin.V2.AutoscalingTargets)\n- [1.22.2](/php/docs/reference/cloud-bigtable/1.22.2/Admin.V2.AutoscalingTargets)\n- [1.21.1](/php/docs/reference/cloud-bigtable/1.21.1/Admin.V2.AutoscalingTargets)\n- [1.20.3](/php/docs/reference/cloud-bigtable/1.20.3/Admin.V2.AutoscalingTargets) \nReference documentation and code samples for the Cloud Bigtable V2 Client class AutoscalingTargets.\n\nThe Autoscaling targets for a Cluster. These determine the recommended nodes.\n\nGenerated from protobuf message `google.bigtable.admin.v2.AutoscalingTargets`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Bigtable \\\\ Admin \\\\ V2\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getCpuUtilizationPercent\n\nThe cpu utilization that the Autoscaler should be trying to achieve.\n\nThis number is on a scale from 0 (no utilization) to\n100 (total utilization), and is limited between 10 and 80, otherwise it\nwill return INVALID_ARGUMENT error.\n\n### setCpuUtilizationPercent\n\nThe cpu utilization that the Autoscaler should be trying to achieve.\n\nThis number is on a scale from 0 (no utilization) to\n100 (total utilization), and is limited between 10 and 80, otherwise it\nwill return INVALID_ARGUMENT error.\n\n### getStorageUtilizationGibPerNode\n\nThe storage utilization that the Autoscaler should be trying to achieve.\n\nThis number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD\ncluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster,\notherwise it will return INVALID_ARGUMENT error. If this value is set to 0,\nit will be treated as if it were set to the default value: 2560 for SSD,\n8192 for HDD.\n\n### setStorageUtilizationGibPerNode\n\nThe storage utilization that the Autoscaler should be trying to achieve.\n\nThis number is limited between 2560 (2.5TiB) and 5120 (5TiB) for a SSD\ncluster and between 8192 (8TiB) and 16384 (16TiB) for an HDD cluster,\notherwise it will return INVALID_ARGUMENT error. If this value is set to 0,\nit will be treated as if it were set to the default value: 2560 for SSD,\n8192 for HDD."]]
