package yb.log

Get desktop application:
View/edit binary Protocol Buffers messages

A batch of entries in the WAL.

• repeated LogEntryPB entry = 1

• optional OpIdPB committed_op_id = 2

• optional uint64 mono_time = 3

  Time when this batch was appended, this time is monotonically increase, and restart safe. I.e. first batch after restart will have time greater than or equal to time of last batch added before restart.

An entry in the WAL/state machine log.

Used in: LogEntryBatchPB

• required LogEntryTypePB type = 1

• optional consensus.ReplicateMsg replicate = 2

Types of log entries.

Used in: LogEntryPB

• UNKNOWN = 0

• REPLICATE = 1

• SYNC_ROLLOVER_MARKER = 998

  Roll over active log segment before writing the next entry if active segment is not empty.

• FLUSH_MARKER = 999

  Serve the purpose of making sure that all entries up to the FLUSH_MARKER entry are flushed.

• ASYNC_ROLLOVER_AT_FLUSH_MARKER = 1000

  Async roll over active log segment, and halve the cur_max_segment_size of the next segment if it's greater than initial_max_segment_size.

A header for a log index block that are stored inside WAL segment file.

• required int64 start_op_index = 1

• required int32 num_entries = 2

• required int64 size = 3

• required bool is_last_block = 4

• required fixed32 crc32c = 5

  CRC32C over log index block of size `size` that follows the serialized header.

A footer for a log segment. Log segment footers might not be present (e.g. if the server crashed) so they should contain no information that cannot be obtained by actually reading the entries in the log. We use the footer to keep sparse index entries mapping op_id->offset (right now we just keep the first entry with an id in the log).

• required int64 num_entries = 1

  The total number of operations inside this segment.

• optional int64 min_replicate_index = 2

  The minimum and maximum index of a REPLICATE message in this segment. NOTE: because of log truncation, the min/max are not necessarily the first/last! For example, a log segment may contain entries "1.5, 1.6, 2.3, 3.3" due to multiple term changes. Because it's possible for a segment to have no REPLICATE messages in it, we set the default to -1 for these fields to avoid accidentally reading 0, which might look like a real log index.

• optional int64 max_replicate_index = 3

• optional int64 close_timestamp_micros = 4

  The time (microseconds since epoch) when this segment was closed. NOTE: in configurations where --skip_wal_rewrite=false is specified, log segments are rewritten during bootstrap, so this field will be reset to the time of the bootstrap in each log segment on a newly-restarted server, rather than copied over from the old log segments.

• optional int64 index_start_offset = 5

  Offset of the first index block. Absence means there is no log index stored in this log segment.

• optional uint64 min_start_time_running_txns = 6

  Minimum start time of running transactions right before closing of the log segment. It can be either of the following values: 1. Minimum start HT of running txns (if any) 2. Tablet leader safe time 3. HybridTime::kInitial if both the previous values were HybridTime::kInvalid or not fetched successfully.

• optional uint64 last_wal_op_log_ht = 7

  Log HT of the last appended WAL Op in the segment.

A header for a log segment.

• required uint32 major_version = 1

  Log format major version.

• required uint32 minor_version = 2

  Log format minor version.

• required bytes unused_tablet_id = 5

  The ID of the tablet this WAL segment stores entries for.

• required int64 sequence_number = 6

  The tablet-specific sequence number of this WAL segment.

• required SchemaPB DEPRECATED_schema = 7

  Schema used when appending entries to this log, and its version.

• optional uint32 DEPRECATED_schema_version = 8