Google Cloud Compute V1 API - Module Google::Cloud::Compute::V1::BackendServiceLocalityLoadBalancingPolicyConfigPolicy::Name (v3.5.0)

Reference documentation and code samples for the Google Cloud Compute V1 API module Google::Cloud::Compute::V1::BackendServiceLocalityLoadBalancingPolicyConfigPolicy::Name.

The name of a locality load-balancing policy. Valid values include ROUND_ROBIN and, for Java clients, LEAST_REQUEST. For information about these values, see the description of localityLbPolicy.

Do not specify the same policy more than once for a backend. If you do, the configuration is rejected.

value: 0
A value indicating that the enum field is not set.

value: 323_318_707

value: 46_604_921
An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests.

value: 119_180_266
This algorithm implements consistent hashing to backends. Maglev can be used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, seeMaglev: A Fast and Reliable Software Network Load Balancer.

value: 166_297_216
Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer.

value: 262_527_171
The load balancer selects a random healthy host.

value: 432_795_069
The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests.

value: 153_895_801
This is a simple policy in which each healthy backend is selected in round robin order. This is the default.

value: 82_501_640
Per-instance weighted Load Balancing via health check reported weights. In internal passthrough network load balancing, it is weighted rendezvous hashing. This option is only supported in internal passthrough network load balancing.

value: 254_930_962
Per-instance weighted Load Balancing via health check reported weights. If set, the Backend Service must configure a non legacy HTTP-based Health Check, and health check replies are expected to contain non-standard HTTP response header field X-Load-Balancing-Endpoint-Weight to specify the per-instance weights. If set, Load Balancing is weighted based on the per-instance weights reported in the last processed health check replies, as long as every instance either reported a valid weight or had UNAVAILABLE_WEIGHT. Otherwise, Load Balancing remains equal-weight. This option is only supported in Network Load Balancing.

value: 5_584_977
Per-endpoint weighted round-robin Load Balancing using weights computed from Backend reported Custom Metrics. If set, the Backend Service responses are expected to contain non-standard HTTP response header field Endpoint-Load-Metrics. The reported metrics to use for computing the weights are specified via the customMetrics fields.