Lines Matching refs:balancer

38 name resolution system, an external load balancer, etc. In any case, the client
57 balancer. The client relies on the load balancer to provide _load
59 should send requests. The balancer updates the server list as needed
61 issues. The load balancer will make any necessary complex decisions and
62 inform the client. The load balancer may communicate with the backend
72 a load balancer to provide load balancing configuration and the list of
73 servers to which the client should send requests. The balancer will update
75 unavailability or health issues. The load balancer will make any necessary
76 complex decisions and inform the client. The load balancer may communicate
81 The load balancer may be separate from the actual server backends and a
82 compromise of the load balancer should only lead to a compromise of the
83 loadbalancing functionality. In other words, a compromised load balancer should
92 load-balancing, where an external load balancer provides simple clients
112    a load balancer address, and a [service config](service_config.md)
116    - Note: If any one of the addresses returned by the resolver is a balancer
126      ignore any balancer addresses returned by the resolver.
128      1. The policy opens a stream to one of the balancer addresses returned
129         by the resolver. It asks the balancer for the server addresses to
132         - Note: In the `grpclb` policy, the non-balancer addresses returned
135      2. The gRPC servers to which the load balancer is directing the client
137         by the load balancer's configuration.
138      3. The load balancer returns a server list to the gRPC client's `grpclb`
145      balancer.  If the server list is empty, the call will block until a