LOGSERVICE_DUMP_PROCESSLIST view is used to monitor the data replay progress and memory usage of each Replication Group (RG) in the Binlog Dump layer. Through this view, users can check the synchronization status, persistence progress, and resource allocation of each RG in real time, helping Ops personnel grasp the real-time operational status of Binlog generation.Field Name | Type | Description |
sid | bigint unsigned | the unique identifier of LogService |
rep_group_id | bigint unsigned | Replication Group ID |
dump_curr_ts_barrier | bigint unsigned | The commit timestamp barrier of the Binlog Dump RG in current memory |
curr_ts_barrier_persisted | bigint unsigned | The current persisted commit timestamp barrier of the Binlog Dump RG |
unpersisted_sql_min_commit_ts | bigint unsigned | The minimum commit timestamp of unpersisted transactions in the current RG |
max_alloc_size | bigint unsigned | the maximum memory allocated to this RG |
used_mem_size | bigint unsigned | the memory used by this RG |
unpersisted_sql_min_commit_ts reflects the earliest transaction timestamp that has not yet been persisted.tdsql > SELECT * FROM INFORMATION_SCHEMA.LOGSERVICE_DUMP_PROCESSLIST LIMIT 1\\G*************************** 1. row ***************************sid: 29635447583932561rep_group_id: 257dump_curr_ts_barrier: 29635448859000901curr_ts_barrier_persisted: 29635448859000901unpersisted_sql_min_commit_ts: NULLmax_alloc_size: 10485760used_mem_size: 01 row in set (0.00 sec)
unpersisted_sql_min_commit_ts is NULL, indicating there are no unpersisted transactions.Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários