Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
LOGSERVICE_DUMP_STAT view displays the overall replay status and performance metrics of the Binlog Dump layer. This view provides detailed resource utilization, time consumption statistics, and persistence progress information, helping Ops personnel comprehensively monitor the operational status of the Binlog Dump service.Field Name | Type | Description |
sid | bigint unsigned | the unique identifier of LogService |
unflush_min_commit_ts | bigint unsigned | The current smallest unpersisted transaction commit timestamp of LogService |
rep_group_num | bigint unsigned | The current number of RGs replayed by LogService |
mc_job_ts_advanced | bigint unsigned | The point in time when the MC job ts advances |
read_from_disk_num | bigint unsigned | The number of times spilled data is read from disk |
dump_max_mem_size | bigint unsigned | The maximum memory allowed for Binlog Dump |
dump_use_mem_size | bigint unsigned | The current memory usage of Binlog Dump |
log_handler_cache_size | bigint unsigned | Log Handler memory usage |
peer_client_cache_size | bigint unsigned | Binlog Dump memory usage |
wait_flush_binlog_cache_size | bigint unsigned | Binlog Thread memory usage |
alloc_from_mem | bigint unsigned | The amount of memory allocated from memory (see alloc_mem_from_file) |
alloc_mem_from_file | bigint unsigned | The amount of memory mapped from files |
binlog_thread_run_time | bigint unsigned | Binlog Thread total time |
flush_binlog_time | bigint unsigned | Binlog Thread writing time from Binlog Cache to Binlog file |
read_from_disk_time | bigint unsigned | The time taken to read spilled data from disk |
decode_record_time | bigint unsigned | Storage layer key/value parsing time |
write_begin_time | bigint unsigned | Time taken to write the begin query event to Binlog Cache |
write_gtid_time | bigint unsigned | Time taken to write the gtid event to Binlog Cache |
write_xid_event_time | bigint unsigned | Time taken to write the xid commit event to Binlog Cache |
write_row_time | bigint unsigned | Time taken to convert table records to row change events |
write_table_map_time | bigint unsigned | Time taken to write the table map event to Binlog Cache |
flush_pending_rows_event_time | bigint unsigned | Time taken to write the row change event to Binlog Cache |
persist_gno | bigint unsigned | current persistent gno |
persist_commit_ts | bigint unsigned | commit ts of the transaction corresponding to the persistent gno |
persist_info_update_ts | varchar(64) | The last point in time of persistence |
flush_bytes | bigint unsigned | The number of bytes of Binlog written by the current process |
binlog_file_write_time | bigint unsigned | Time taken for the write system call to write Binlog files |
binlog_file_flush_time | bigint unsigned | Time taken for the flush system call to write Binlog files |
binlog_file_sync_time | bigint unsigned | Time taken for the sync system call to write Binlog files |
flush_rate(MB/s) | bigint unsigned | Rate of flushing to disk via the flush system call |
dump_use_mem_size to dump_max_mem_size can be used to evaluate memory utilization.persist_commit_ts and persist_info_update_ts display the data persistence status.flush_bytes statistics on cumulative write volume.tdsql > SELECT * FROM INFORMATION_SCHEMA.LOGSERVICE_DUMP_STAT\\G*************************** 1. row ***************************sid: 29629282460369180unflush_min_commit_ts: NULLrep_group_num: 2mc_job_ts_advanced: 29629300260995193read_from_disk_num: 14dump_max_mem_size: 16788990976dump_use_mem_size: 62914560log_handler_cache_size: 0peer_client_cache_size: 0wait_flush_binlog_cache_size: 0alloc_from_mem: 0alloc_mem_from_file: 0binlog_thread_run_time: 18flush_binlog_time: 2read_from_disk_time: 2decode_record_time: 6write_begin_time: 0write_gtid_time: 0write_xid_event_time: 0write_row_time: 4write_table_map_time: 0flush_pending_rows_event_time: 0persist_gno: 27persist_commit_ts: 29629299858342126persist_info_update_ts: 2025-12-18 15:45:09flush_bytes: 707677465binlog_file_write_time: 0binlog_file_flush_time: 0binlog_file_sync_time: 0flush_rate(MB/s): 01 row in set (0.00 sec)
피드백