Get desktop application:
View/edit binary Protocol Buffers messages
Bidirectional rpc to get a list of servers.
This message should be sent on the first request to the load balancer.
The client stats should be periodically reported to the load balancer based on the duration defined in the InitialLoadBalanceResponse.
This message should be sent on the first response to the client.
Contains the list of servers selected by the load balancer. The client should send requests to these servers in the specified order.
Contains client level statistics that are useful to load balancing. Each count except the timestamp should be reset to zero after reporting the stats.
Used in:
The timestamp of generating the report.
The total number of RPCs that started.
The total number of RPCs that finished.
The total number of RPCs that failed to reach a server except dropped RPCs.
The total number of RPCs that finished and are known to have been received by a server.
The list of dropped calls.
Contains the number of calls finished for a particular load balance token.
Used in:
See Server.load_balance_token.
The total number of RPCs that finished associated with the token.
Used in:
Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive.
Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0 `seconds` field and a positive or negative `nanos` field. For durations of one second or more, a non-zero value for the `nanos` field must be of the same sign as the `seconds` field. Must be from -999,999,999 to +999,999,999 inclusive.
Used in:
Name of load balanced service (IE, balancer.service.com) length should be less than 256 bytes.
Used in:
This is an application layer redirect that indicates the client should use the specified server for load balancing. When this field is non-empty in the response, the client should open a separate connection to the load_balancer_delegate and call the BalanceLoad method. Its length should be less than 64 bytes.
This interval defines how often the client should send the client stats to the load balancer. Stats should only be reported when the duration is positive.
Contains server information. When the drop field is not true, use the other fields.
Used in:
A resolved address for the server, serialized in network-byte-order. It may either be an IPv4 or IPv6 address.
A resolved port number for the server.
An opaque but printable token given to the frontend for each pick. All frontend requests for that pick must include the token in its initial metadata. The token is used by the backend to verify the request and to allow the backend to report load to the gRPC LB system. The token is also used in client stats for reporting dropped calls. Its length is variable but less than 50 bytes.
Indicates whether this particular request should be dropped by the client. If the request is dropped, there will be a corresponding entry in ClientStats.calls_finished_with_drop.
Used in:
Contains a list of servers selected by the load balancer. The list will be updated when server resolutions change or as needed to balance load across more servers. The client should consume the server list in order unless instructed otherwise via the client_config.
Used in:
Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.