Cloud Bigtable V2 Client - Class MultiClusterRoutingUseAny (1.24.1)

Reference documentation and code samples for the Cloud Bigtable V2 Client class MultiClusterRoutingUseAny.

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.

Generated from protobuf message google.bigtable.admin.v2.AppProfile.MultiClusterRoutingUseAny

Namespace

Google \ Cloud \ Bigtable \ Admin \ V2 \ AppProfile

Methods

__construct

Constructor.

Parameters
NameDescription
data array

Optional. Data for populating the Message object.

↳ cluster_ids array

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.

getClusterIds

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.

Returns
TypeDescription
Google\Protobuf\Internal\RepeatedField

setClusterIds

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.

Parameter
NameDescription
var string[]
Returns
TypeDescription
$this