package slog.internal

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

message Batch

internal.proto:7

Used in: ForwardBatchData

message BatchReplicationAck

internal.proto:121

Used in: Request

message BrokerRedirect

internal.proto:89

Used in: Request

message Configuration

configuration.proto:134

* The schema of a configuration file.

message CpuPinning

configuration.proto:105

Used in: Configuration

message Envelope

internal.proto:34

enum ExecutionType

configuration.proto:125

Used in: Configuration

message FinishedSubtransaction

internal.proto:151

Used in: Request

message ForwardBatchData

internal.proto:104

Used in: Request

message ForwardBatchOrder

internal.proto:114

Used in: Request

message ForwardTransaction

internal.proto:95

Used in: Request

message GraphLog

internal.proto:168

Used in: Request

message GraphLogEntry

internal.proto:161

Used in: GraphLog

message HashPartitioning

configuration.proto:45

* With hash partitioning, each key is interpreted as a byte string. The keys are distributed to the partitions based on their hash values. Initial data can be loaded from an external file.

Used in: Configuration

message JanusAcceptRequest

internal.proto:183

Used in: Request

message JanusAcceptResponse

internal.proto:258

Used in: Response

message JanusCommit

internal.proto:189

Used in: Request

message JanusDependency

internal.proto:172

Used in: JanusAcceptRequest, JanusCommit, JanusInquiryResult, JanusPreAcceptResponse

message JanusInquireRequest

internal.proto:195

Used in: Request

message JanusInquireResponse

internal.proto:269

Used in: Response

message JanusInquiryResult

internal.proto:263

Used in: JanusInquireResponse

message JanusPreAcceptRequest

internal.proto:178

Used in: Request

message JanusPreAcceptResponse

internal.proto:252

Used in: Response

message KeyMasterMetadata

internal.proto:228

Used in: LookupMasterResponse

message LocalBatchOrder

internal.proto:19

Used in: ForwardBatchOrder

message LookupMasterRequest

internal.proto:99

Used in: Request

message LookupMasterResponse

internal.proto:233

Used in: Response

message MetricOptions

configuration.proto:110

Used in: Configuration

message PaxosAcceptRequest

internal.proto:129

Used in: Request

message PaxosAcceptResponse

internal.proto:238

Used in: Response

message PaxosCommitRequest

internal.proto:135

Used in: Request

message PaxosCommitResponse

internal.proto:243

Used in: Response

message PaxosPropose

internal.proto:125

Used in: Request

message Ping

internal.proto:78

Used in: Request

message Pong

internal.proto:222

* For debugging and testing purposes

Used in: Response

message Region

configuration.proto:8

Used in: Configuration

message RemoteBatchOrder

internal.proto:27

Used in: ForwardBatchOrder

message RemoteReadResult

internal.proto:141

Used in: Request

message ReplicationDelayExperiment

configuration.proto:32

Used in: Configuration

message Request

internal.proto:53

* The first message of a communication between two entities is always a Request. Some types of Request needs a Response (e.g. LookUpMasterRequest); names of these requests end with "Request". Some others are one-way requests (e.g. PaxosPropose) and do not end with "Request".

Used in: Envelope

message Response

internal.proto:205

* A response is always preceeded by a Request

Used in: Envelope

message Signal

internal.proto:86

* Generic signal message

Used in: Request

(message has no fields)

message SimplePartitioning

configuration.proto:66

* With simple partitioning, each key is assumed to be a number. The keys are distributed to the partitions based on key values modulo the number of partitions. Initial data cannot be loaded from an external file but can be generated at startup. The following is an example of home and partition assignment of the generated data with 3 partitions and 4 regions. home | 0 1 2 3 0 1 2 3 0 ... ------------|------------------------------- partition 0 | 0 3 6 9 12 15 18 21 24 ... partition 1 | 1 4 7 10 13 16 19 22 25 ... partition 2 | 2 5 8 11 14 17 20 23 26 ... ------------|------------------------------- | keys

Used in: Configuration

message SimplePartitioning2

configuration.proto:89

* With simple partitioning, each key is assumed to be a number. The keys are distributed to the regions based on key values modulo the number of regions. Initial data cannot be loaded from an external file but can be generated at startup. The following is an example of home and partition assignment of the generated data with 3 partitions and 4 regions. partition | 0 1 2 3 0 1 2 3 0 ... ------------|------------------------------- home 0 | 0 3 6 9 12 15 18 21 24 ... home 1 | 1 4 7 10 13 16 19 22 25 ... home 2 | 2 5 8 11 14 17 20 23 26 ... ------------|------------------------------- | keys

Used in: Configuration

message StatsRequest

internal.proto:156

Used in: Request

message StatsResponse

internal.proto:247

Used in: Response

message TPCCPartitioning

configuration.proto:100

* Similar to simple partitioning but instead of using the whole key, only the warehouse id portion of the key is used for partitioning.

Used in: Configuration