Class: Google::Cloud::Bigtable::Admin::V2::AppProfile::MultiClusterRoutingUseAny
- Inherits:
-
Object
- Object
- Google::Cloud::Bigtable::Admin::V2::AppProfile::MultiClusterRoutingUseAny
- Extended by:
- Protobuf::MessageExts::ClassMethods
- Includes:
- Protobuf::MessageExts
- Defined in:
- proto_docs/google/bigtable/admin/v2/instance.rb
Overview
Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability.
Defined Under Namespace
Classes: RowAffinity
Instance Attribute Summary collapse
-
#cluster_ids ⇒ ::Array<::String>
The set of clusters to route to.
-
#row_affinity ⇒ ::Google::Cloud::Bigtable::Admin::V2::AppProfile::MultiClusterRoutingUseAny::RowAffinity
Row affinity sticky routing based on the row key of the request.
Instance Attribute Details
#cluster_ids ⇒ ::Array<::String>
Returns The set of clusters to route to. The order is ignored; clusters will be tried in order of distance. If left empty, all clusters are eligible.
317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 |
# File 'proto_docs/google/bigtable/admin/v2/instance.rb', line 317 class MultiClusterRoutingUseAny include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # If enabled, Bigtable will route the request based on the row key of the # request, rather than randomly. Instead, each row key will be assigned # to a cluster, and will stick to that cluster. If clusters are added or # removed, then this may affect which row keys stick to which clusters. # To avoid this, users can use a cluster group to specify which clusters # are to be used. In this case, new clusters that are not a part of the # cluster group will not be routed to, and routing will be unaffected by # the new cluster. Moreover, clusters specified in the cluster group cannot # be deleted unless removed from the cluster group. class RowAffinity include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end end |
#row_affinity ⇒ ::Google::Cloud::Bigtable::Admin::V2::AppProfile::MultiClusterRoutingUseAny::RowAffinity
Returns Row affinity sticky routing based on the row key of the request. Requests that span multiple rows are routed non-deterministically.
317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 |
# File 'proto_docs/google/bigtable/admin/v2/instance.rb', line 317 class MultiClusterRoutingUseAny include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods # If enabled, Bigtable will route the request based on the row key of the # request, rather than randomly. Instead, each row key will be assigned # to a cluster, and will stick to that cluster. If clusters are added or # removed, then this may affect which row keys stick to which clusters. # To avoid this, users can use a cluster group to specify which clusters # are to be used. In this case, new clusters that are not a part of the # cluster group will not be routed to, and routing will be unaffected by # the new cluster. Moreover, clusters specified in the cluster group cannot # be deleted unless removed from the cluster group. class RowAffinity include ::Google::Protobuf::MessageExts extend ::Google::Protobuf::MessageExts::ClassMethods end end |