Get desktop application:
View/edit binary Protocol Buffers messages
Find the keyspace group that the keyspace belongs to.
V1/V2 compatibility keyspace id. V3 should use keyspace_identity.
V3 keyspace identity.
Get the minimum timestamp across all keyspace groups served by the TSO server who receives and handle the request. If the TSO server/pod is not serving any keyspace group, return an empty timestamp, and the client needs to skip the empty timestamps when collecting the min timestamp from all TSO servers/pods.
the count of keyspace group primaries that the TSO server/pod is serving
the total count of keyspace groups
Used in:
Used in:
Used in:
Used in:
name is the unique name of the TSO participant.
id is the unique id of the TSO participant.
listen_urls is the serivce endpoint list in the url format. listen_urls[0] is primary service endpoint.
Used in: , ,
cluster_id is the ID of the cluster which be sent to.
sender_id is the ID of the sender server.
keyspace_id is the unique id of the tenant/keyspace in V1/V2. V3 should use keyspace_identity and must not read this legacy field as the full identity.
V3 keyspace identity of the request.
keyspace_group_id is the unique id of the keyspace group to which the tenant/keyspace belongs.
callee_id is the ID of the server which the client expects to receive the request. such as tso-0, tso-1, pd-0, pd-1 etc. This field is used to check if the request is sent to the expected server. If it is not matched, the server will return an error.
Used in: , ,
cluster_id is the ID of the cluster which sent the response.
keyspace_id is the unique id of the tenant/keyspace as the response receiver in V1/V2. V3 should use keyspace_identity and must not read this legacy field as the full identity.
V3 keyspace identity served by this response.
keyspace_group_id is the unique id of the keyspace group to which the tenant/keyspace belongs.
Used in: