proto_docs/google/bigtable/admin/v2/instance.rb in google-cloud-bigtable-admin-v2-1.3.0 vs proto_docs/google/bigtable/admin/v2/instance.rb in google-cloud-bigtable-admin-v2-1.4.0

- old
+ new

@@ -157,10 +157,13 @@ # Output only. The current state of the cluster. # @!attribute [rw] serve_nodes # @return [::Integer] # The number of nodes allocated to this cluster. More nodes enable higher # throughput and more consistent performance. + # @!attribute [rw] node_scaling_factor + # @return [::Google::Cloud::Bigtable::Admin::V2::Cluster::NodeScalingFactor] + # Immutable. The node scaling factor of this cluster. # @!attribute [rw] cluster_config # @return [::Google::Cloud::Bigtable::Admin::V2::Cluster::ClusterConfig] # Configuration for this cluster. # @!attribute [rw] default_storage_type # @return [::Google::Cloud::Bigtable::Admin::V2::StorageType] @@ -234,9 +237,24 @@ RESIZING = 3 # The cluster has no backing nodes. The data (tables) still # exist, but no operations can be performed on the cluster. DISABLED = 4 + end + + # Possible node scaling factors of the clusters. Node scaling delivers better + # latency and more throughput by removing node boundaries. + module NodeScalingFactor + # No node scaling specified. Defaults to NODE_SCALING_FACTOR_1X. + NODE_SCALING_FACTOR_UNSPECIFIED = 0 + + # The cluster is running with a scaling factor of 1. + NODE_SCALING_FACTOR_1X = 1 + + # The cluster is running with a scaling factor of 2. + # All node count values must be in increments of 2 with this scaling factor + # enabled, otherwise an INVALID_ARGUMENT error will be returned. + NODE_SCALING_FACTOR_2X = 2 end end # A configuration object describing how Cloud Bigtable should treat traffic # from a particular end user application.