Module: Google::Cloud::Compute::V1::BackendServiceLocalityLoadBalancingPolicyConfigPolicy::Name

Defined in:

proto_docs/google/cloud/compute/v1/compute.rb

Overview

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.

Constant Summary

UNDEFINED_NAME =

A value indicating that the enum field is not set.

0

INVALID_LB_POLICY =

323_318_707

LEAST_REQUEST =

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

46_604_921

MAGLEV =

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, see https://ai.google/research/pubs/pub44824

119_180_266

ORIGINAL_DESTINATION =

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.

166_297_216

RANDOM =

The load balancer selects a random healthy host.

262_527_171

RING_HASH =

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.

432_795_069

ROUND_ROBIN =

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

153_895_801

WEIGHTED_MAGLEV =

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.

254_930_962