Format of clogs

This topic describes the print format of clogs.

Generally, a clog file contains many types of logs. As the predominant log type, OB_LOG_SUBMIT indicates the logs committed by modules other than the clog module, including the clogs committed by a transaction module.

A clog consists of three parts: abstract, header, and content. See the following template log format:

$$$abstract |header |||   |||content

Abstract

The abstract describes the information about a log record in a log file, as shown in the following example:

file_id:*** offset:*** len:***  OB_LOG_SUBMIT

The following table describes the fields.

Header

The header describes the information about the log record itself, as shown in the following example:

ObLogEntryHeader:{magic:***, version:***, type:***, partition_key:***, log_id:***, data_len:***, generation_timestamp:***, epoch_id:***, proposal_id:***, submit_timestamp:***, is_batch_committed:***, is_trans_log:***, data_checksum:***, active_memstore_version:***, header_checksum:***}

The following table describes some fields.

Entity

The content describes the data contained in the log record, as shown in the following example:

Trans: log_type:***, trans_inc:*** {[trans_log]}||| [mutator]

The following table describes some fields.