Lines Matching refs:backends

48 server backends, running the client, and then querying the client's
83 `num_rpcs` responses received from backends, as different backends may respond
100 1.  4 backends are created in a single managed instance group (MIG).
104 1.  All backends receive at least one RPC
119 1.  4 backends are created in a single MIG.
123 1.  Once all backends receive at least one RPC, the following 100 RPCs are
124     evenly distributed across the 4 backends.
129 of backends that is stopped and then resumed.
138 1.  4 backends are created in a single MIG.
142 1.  All backends receive at least one RPC.
145 then stops the backends.
151 The test driver resumes the backends.
155 1.  Once all backends receive at least one RPC, the distribution for a block of
160 This test verifies that backends in a secondary locality receive traffic when
161 all backends in the primary locality fail.
170 1.  The primary MIG with 2 backends in the same zone as the client
171 1.  The secondary MIG with 2 backends in a different zone
175 1.  All backends in the primary locality receive at least 1 RPC.
176 1.  No backends in the secondary locality receive RPCs.
178 The test driver stops the backends in the primary locality.
182 1.  All backends in the secondary locality receive at least 1 RPC.
184 The test driver resumes the backends in the primary locality.
188 1.  All backends in the primary locality receive at least 1 RPC.
189 1.  No backends in the secondary locality receive RPCs.
193 This test verifies that backends in a failover locality do not receive traffic
194 when at least one of the backends in the primary locality remain healthy.
206 1.  The primary MIG with 2 backends in the same zone as the client
207 1.  The secondary MIG with 2 backends in a different zone
211 1.  All backends in the primary locality receive at least 1 RPC.
212 1.  No backends in the secondary locality receive RPCs.
214 The test driver stops one of the backends in the primary locality.
218 1.  All backends in the primary locality receive at least 1 RPC.
219 1.  No backends in the secondary locality receive RPCs.
234 1.  One MIG with two backends, using rate balancing mode.
238 1.  All backends receive at least one RPC.
240 The test driver adds a new MIG with two backends in the same zone.
244 1.  All backends in each MIG receive at least one RPC.
258 1.  Two MIGs with two backends each, using rate balancing mode.
262 1.  All backends receive at least one RPC.
268 1.  All RPCs are directed to the two remaining backends (no RPC failures).
273 to the new backends.
283 1.  One MIG with two backends
287 1.  All backends receive at least one RPC.
289 The test driver creates a new backend service containing a MIG with two backends
313 1. Once all backends receive at least one RPC, the following 1000 RPCs are
321 1. Once all backends receive at least one RPC, the following 1000 RPCs are
322 distributed across the 2 backends as a: 20, b: 80.