tencent cloud

TDSQL Boundless

DocumentaçãoTDSQL BoundlessGeneral ReferenceSQL ReferenceData DictionaryINFORMATION_SCHEMALOGSERVICE_DUMP_STAT

LOGSERVICE_DUMP_STAT

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2026-03-06 18:48:07

Function

The 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 Description

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
Key Metrics Description
1. Memory Usage Monitoring
The ratio of dump_use_mem_size to dump_max_mem_size can be used to evaluate memory utilization.
Memory usage of each component (log_handler, peer_client, binlog_thread) helps locate time consumption issues.
2. Performance Bottleneck Analysis
Stage-wise time consumption statistics can identify performance bottlenecks.
Disk I/O related metrics (flush_rate) reflect storage performance.
3. Persistence Progress
persist_commit_ts and persist_info_update_ts display the data persistence status.
flush_bytes statistics on cumulative write volume.

Examples

tdsql > SELECT * FROM INFORMATION_SCHEMA.LOGSERVICE_DUMP_STAT\\G
*************************** 1. row ***************************
                          sid: 29629282460369180
        unflush_min_commit_ts: NULL
                rep_group_num: 2
           mc_job_ts_advanced: 29629300260995193
           read_from_disk_num: 14
            dump_max_mem_size: 16788990976
            dump_use_mem_size: 62914560
       log_handler_cache_size: 0
       peer_client_cache_size: 0
 wait_flush_binlog_cache_size: 0
               alloc_from_mem: 0
          alloc_mem_from_file: 0
       binlog_thread_run_time: 18
            flush_binlog_time: 2
          read_from_disk_time: 2
           decode_record_time: 6
             write_begin_time: 0
              write_gtid_time: 0
         write_xid_event_time: 0
               write_row_time: 4
         write_table_map_time: 0
flush_pending_rows_event_time: 0
                  persist_gno: 27
            persist_commit_ts: 29629299858342126
       persist_info_update_ts: 2025-12-18 15:45:09
                  flush_bytes: 707677465
       binlog_file_write_time: 0
       binlog_file_flush_time: 0
        binlog_file_sync_time: 0
             flush_rate(MB/s): 0
1 row in set (0.00 sec)
Result Interpretation
The current service manages 2 RGs with low memory utilization (62MB/16GB).
The data has been persisted to gno=27, corresponding to commit ts=29629299858342126.
Approximately 675MB of Binlog data has been cumulatively written.
The system operational status is normal, with all metrics within acceptable ranges.
Anterior: LOGSERVICE_DUMP_PROCESSLISTPróximo: LOGSERVICE_ELAPSED

Ajuda e Suporte

Esta página foi útil?

comentários