Class: Google::Cloud::Bigtable::Admin::V2::AppProfile::MultiClusterRoutingUseAny

Inherits:
Object
  • Object
show all
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

Instance Attribute Details

#cluster_ids ⇒ ::Array<::String> 



349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
 
# File 'proto_docs/google/bigtable/admin/v2/instance.rb', line 349

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 



349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
 
# File 'proto_docs/google/bigtable/admin/v2/instance.rb', line 349

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