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
[[["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 2025-09-04 UTC."],[],[],null,["# Cloud Bigtable V2 Client - Class MultiClusterRoutingUseAny (2.17.1)\n\nVersion latestkeyboard_arrow_down\n\n- [2.17.1 (latest)](/php/docs/reference/cloud-bigtable/latest/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.17.0](/php/docs/reference/cloud-bigtable/2.17.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.16.0](/php/docs/reference/cloud-bigtable/2.16.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.15.0](/php/docs/reference/cloud-bigtable/2.15.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.14.0](/php/docs/reference/cloud-bigtable/2.14.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.13.0](/php/docs/reference/cloud-bigtable/2.13.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.12.0](/php/docs/reference/cloud-bigtable/2.12.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.11.1](/php/docs/reference/cloud-bigtable/2.11.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.9.1](/php/docs/reference/cloud-bigtable/2.9.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.8.0](/php/docs/reference/cloud-bigtable/2.8.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.7.0](/php/docs/reference/cloud-bigtable/2.7.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.6.3](/php/docs/reference/cloud-bigtable/2.6.3/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.5.0](/php/docs/reference/cloud-bigtable/2.5.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.4.0](/php/docs/reference/cloud-bigtable/2.4.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.3.0](/php/docs/reference/cloud-bigtable/2.3.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.2.1](/php/docs/reference/cloud-bigtable/2.2.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.1.0](/php/docs/reference/cloud-bigtable/2.1.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [2.0.1](/php/docs/reference/cloud-bigtable/2.0.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.32.1](/php/docs/reference/cloud-bigtable/1.32.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.31.1](/php/docs/reference/cloud-bigtable/1.31.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.30.0](/php/docs/reference/cloud-bigtable/1.30.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.29.2](/php/docs/reference/cloud-bigtable/1.29.2/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.28.3](/php/docs/reference/cloud-bigtable/1.28.3/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.27.0](/php/docs/reference/cloud-bigtable/1.27.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.26.2](/php/docs/reference/cloud-bigtable/1.26.2/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.25.0](/php/docs/reference/cloud-bigtable/1.25.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.24.1](/php/docs/reference/cloud-bigtable/1.24.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.23.0](/php/docs/reference/cloud-bigtable/1.23.0/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.22.2](/php/docs/reference/cloud-bigtable/1.22.2/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.21.1](/php/docs/reference/cloud-bigtable/1.21.1/Admin.V2.AppProfile.MultiClusterRoutingUseAny)\n- [1.20.3](/php/docs/reference/cloud-bigtable/1.20.3/Admin.V2.AppProfile.MultiClusterRoutingUseAny) \nReference documentation and code samples for the Cloud Bigtable V2 Client class MultiClusterRoutingUseAny.\n\nRead/write requests are routed to the nearest cluster in the instance, and\nwill fail over to the nearest cluster that is available in the event of\ntransient errors or delays. Clusters in a region are considered\nequidistant. Choosing this option sacrifices read-your-writes consistency\nto improve availability.\n\nGenerated from protobuf message `google.bigtable.admin.v2.AppProfile.MultiClusterRoutingUseAny`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Bigtable \\\\ Admin \\\\ V2 \\\\ AppProfile\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getClusterIds\n\nThe set of clusters to route to. The order is ignored; clusters will be\ntried in order of distance. If left empty, all clusters are eligible.\n\n### setClusterIds\n\nThe set of clusters to route to. The order is ignored; clusters will be\ntried in order of distance. If left empty, all clusters are eligible.\n\n### getRowAffinity\n\nRow affinity sticky routing based on the row key of the request.\n\nRequests that span multiple rows are routed non-deterministically.\n\n### hasRowAffinity\n\n### setRowAffinity\n\nRow affinity sticky routing based on the row key of the request.\n\nRequests that span multiple rows are routed non-deterministically.\n\n### getAffinity"]]