package Etcd

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service Auth

router.proto:136

service Cluster

router.proto:78

service Election

router.proto:1063

The election service exposes client-side election facilities as a gRPC interface.

service Health

router.proto:993

service KV

router.proto:12

service Lease

router.proto:53

service Lock

router.proto:1045

The lock service exposes client-side locking facilities as a gRPC interface.

service Maintenance

router.proto:100

service Watch

router.proto:43

message AlarmMember

router.proto:790

Used in: AlarmResponse

enum AlarmRequest.AlarmAction

router.proto:774

Used in: AlarmRequest

enum AlarmType

router.proto:767

Used in: AlarmMember, AlarmRequest

message Compare

router.proto:366

Used in: TxnRequest

enum Compare.CompareResult

router.proto:367

Used in: Compare

enum Compare.CompareTarget

router.proto:373

Used in: Compare

message DeleteRangeRequest

router.proto:323

Used as request type in: KV.DeleteRange

Used as field type in: RequestOp

message DeleteRangeResponse

router.proto:338

Used as response type in: KV.DeleteRange

Used as field type in: ResponseOp

message HealthCheckRequest

router.proto:979

Used as request type in: Health.Check, Health.Watch

message HealthCheckResponse

router.proto:983

Used as response type in: Health.Check, Health.Watch

enum HealthCheckResponse.ServingStatus

router.proto:984

Used in: HealthCheckResponse

message LeaderKey

router.proto:1104

Used in: CampaignResponse, ProclaimRequest, ResignRequest

message LeaderRequest

router.proto:1118

Used as request type in: Election.Leader, Election.Observe

message LeaderResponse

router.proto:1123

Used as response type in: Election.Leader, Election.Observe

message LeaseCheckpoint

router.proto:618

Used in: LeaseCheckpointRequest

message LeaseCheckpointRequest

router.proto:626

message LeaseCheckpointResponse

router.proto:630

message LeaseStatus

router.proto:669

Used in: LeaseLeasesResponse

message Member

router.proto:679

Used in: MemberAddResponse, MemberListResponse, MemberPromoteResponse, MemberRemoveResponse, MemberUpdateResponse

message PutRequest

router.proto:295

Used as request type in: KV.Put

Used as field type in: RequestOp

message PutResponse

router.proto:317

Used as response type in: KV.Put

Used as field type in: ResponseOp

message RangeRequest

router.proto:217

Used as request type in: KV.Range

Used as field type in: RequestOp

enum RangeRequest.SortOrder

router.proto:218

Used in: RangeRequest

enum RangeRequest.SortTarget

router.proto:223

Used in: RangeRequest

message RangeResponse

router.proto:284

Used as response type in: KV.Range

Used as field type in: ResponseOp

message RequestOp

router.proto:346

Used in: TxnRequest

message ResponseHeader

router.proto:203

Used in: AlarmResponse, AuthDisableResponse, AuthEnableResponse, AuthRoleAddResponse, AuthRoleDeleteResponse, AuthRoleGetResponse, AuthRoleGrantPermissionResponse, AuthRoleListResponse, AuthRoleRevokePermissionResponse, AuthUserAddResponse, AuthUserChangePasswordResponse, AuthUserDeleteResponse, AuthUserGetResponse, AuthUserGrantRoleResponse, AuthUserListResponse, AuthUserRevokeRoleResponse, AuthenticateResponse, CampaignResponse, CompactionResponse, DefragmentResponse, DeleteRangeResponse, HashKVResponse, HashResponse, LeaderResponse, LeaseCheckpointResponse, LeaseGrantResponse, LeaseKeepAliveResponse, LeaseLeasesResponse, LeaseRevokeResponse, LeaseTimeToLiveResponse, LockResponse, MemberAddResponse, MemberListResponse, MemberPromoteResponse, MemberRemoveResponse, MemberUpdateResponse, MoveLeaderResponse, ProclaimResponse, PutResponse, RangeResponse, ResignResponse, SnapshotResponse, StatusResponse, TxnResponse, UnlockResponse, WatchResponse

message ResponseOp

router.proto:356

Used in: TxnResponse

message TxnRequest

router.proto:421

From google paxosdb paper: Our implementation hinges around a powerful primitive which we call MultiOp. All other database operations except for iteration are implemented as a single call to MultiOp. A MultiOp is applied atomically and consists of three components: 1. A list of tests called guard. Each test in guard checks a single entry in the database. It may check for the absence or presence of a value, or compare with a given value. Two different tests in the guard may apply to the same or different entries in the database. All tests in the guard are applied and MultiOp returns the results. If all tests are true, MultiOp executes t op (see item 2 below), otherwise it executes f op (see item 3 below). 2. A list of database operations called t op. Each operation in the list is either an insert, delete, or lookup operation, and applies to a single database entry. Two different operations in the list may apply to the same or different entries in the database. These operations are executed if guard evaluates to true. 3. A list of database operations called f op. Like t op, but executed if guard evaluates to false.

Used as request type in: KV.Txn

Used as field type in: RequestOp

message TxnResponse

router.proto:434

Used as response type in: KV.Txn

Used as field type in: ResponseOp

message WatchCancelRequest

router.proto:549

Used in: WatchRequest

message WatchCreateRequest

router.proto:504

Used in: WatchRequest

enum WatchCreateRequest.FilterType

router.proto:524

Used in: WatchCreateRequest

message WatchProgressRequest

router.proto:556

Requests the a watch stream progress status be sent in the watch response stream as soon as possible.

Used in: WatchRequest

(message has no fields)