A cluster represents the actual Cloud Bigtable service. Each cluster belongs to a single Cloud
Bigtable instance. When your application sends requests to a Cloud Bigtable instance, those
requests are actually handled by one of the clusters in the instance.
Each cluster is located in a single zone. An instance's clusters must be in unique zones that
are within the same region. For example, if the first cluster is in us-east1-b, then us-east1-c
is a valid zone for the second cluster. For a list of zones and regions where Cloud Bigtable is
available, see Cloud Bigtable
Locations.
Examples:
// Small production instance:
CreateClusterRequest clusterRequest = CreateClusterRequest.of("my-existing-instance", "my-cluster")
.setZone("us-east1-c")
.setServeNodes(3)
.setStorageType(StorageType.SSD);
Sets the Google Cloud Key Management Service (KMS) key for a CMEK-protected Bigtable. This
requires the full resource name of the Cloud KMS key, in the format
projects/{key_project_id}/locations/{location}/keyRings/{ring_name}/cryptoKeys/{key_name}
Sets the scaling node to manual and sets the number of nodes allocated to this cluster. More
nodes enable higher throughput and more consistent performance.
[[["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 2024-12-05 UTC."],[],[]]
