tencent cloud

TDSQL Boundless

LOGSERVICE_ELAPSED

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

Function

The INFORMATION_SCHEMA.LOGSERVICE_ELAPSED view is used to monitor and analyze the time consumption performance of each Replication Group (RG) during binlog generation in disaster recovery environments. This view details the time consumption of key stages in the log processing pipeline, helping you identify performance bottlenecks in data synchronization and optimize the efficiency of disaster recovery links/binlog generation.

Field Description

Field Name
Type
Description
sid
bigint unsigned
the unique identifier of LogService
rep_group_id
bigint unsigned
the ID of the Replication Group (RG)
IsRunning
bigint unsigned
Log Handler total time spent in running state
DecodeKV
bigint unsigned
Key-Value parsing time
SendLog
bigint unsigned
Time to send Binlog to peer Client
GetUserRgList
bigint unsigned
User RG list retrieval time
SendMsg
bigint unsigned
Time to send messages to peer Client
UpdateCommitTsBarrier
bigint unsigned
Time to update the commit timestamp barrier
WaitParentRg
bigint unsigned
Time spent waiting for parent Replication Group data to be ready
WaitVanishedRgDispatch
bigint unsigned
Time spent waiting for removed Replication Group scheduling
WaitSysRgOrVanishedRgCommitTsAdvance
bigint unsigned
Time spent waiting for the commit timestamp advancement of system Replication Groups or removed Replication Groups
WaitUsrRgCommitTsAdvance
bigint unsigned
Time spent waiting for the commit timestamp advancement of User Replication Groups
GetVanishedRgMinBarrier
bigint unsigned
Time to obtain the minimum barrier for the removed Replication Group
WaitRaftLog
bigint unsigned
Time spent waiting for Raft log synchronization
GetMergeLogJobIdStat
bigint unsigned
Time to obtain the status of log merging tasks
WaitAllMergeLogApplied
bigint unsigned
Time spent waiting for all merged logs to complete replay
GetRaftLogFromBackup
bigint unsigned
Reserved field is not used in the current version.
WaitRaftNodeShutDown
bigint unsigned
Reserved field is not used in the current version.
GetRaftLogFromBackupFinish
bigint unsigned
Reserved field is not used in the current version.
RaftOnApply
bigint unsigned
Reserved field is not used in the current version.
BackupRaftApply
bigint unsigned
Reserved field is not used in the current version.
WaitCachedMsgConsumed
bigint unsigned
Time spent waiting for cached messages to be consumed in Binlog Dump mode
WaitGlobalTsBarrierAdvanced
bigint unsigned
Time spent waiting for the global timestamp barrier to advance in Binlog Dump mode
WaitAllRepGroupRun
bigint unsigned
Time spent waiting for all replication groups to start replaying in Binlog Dump mode
GetRaftLogFromBackupInExitProcess
bigint unsigned
Reserved field is not used in the current version.
BatchKVFlushToDisk
bigint unsigned
Time spent flushing Key-Value data to disk in batches when memory usage is excessively high
Note:
The unit for all time-consuming fields is seconds (s).
By analyzing the proportion of time consumed at each stage, the specific phase where performance bottlenecks occur can be identified.

Examples

tdsql > SELECT * FROM INFORMATION_SCHEMA.LOGSERVICE_ELAPSED LIMIT 1\\G
*************************** 1. row ***************************
sid: 29629282460369180
rep_group_id: 257
IsRunning: 6
DecodeKV: 13
SendLog: 0
GetUserRgList: 0
SendMsg: 3
UpdateCommitTsBarrier: 0
WaitParentRg: 0
WaitVanishedRgDispatch: 0
WaitSysRgOrVanishedRgCommitTsAdvance: 10
WaitUsrRgCommitTsAdvance: 0
GetVanishedRgMinBarrier: 0
WaitRaftLog: 1017
GetMergeLogJobIdStat: 0
WaitAllMergeLogApplied: 0
GetRaftLogFromBackup: 0
WaitRaftNodeShutDown: 0
GetRaftLogFromBackupFinish: 0
RaftOnApply: 0
BackupRaftApply: 0
WaitCachedMsgConsumed: 0
WaitGlobalTsBarrierAdvanced: 0
WaitAllRepGroupRun: 0
GetRaftLogFromBackupInExitProcess: 0
BatchKVFlushToDisk: 5
1 row in set (0.00 sec)
Result interpretation:
The primary time consumption of the replication group (ID: 257) is concentrated in WaitRaftLog (1017s), indicating that Raft log synchronization is the current main bottleneck.
DecodeKV and BatchKVFlushToDisk also incurred some time, indicating the overhead of decoding and disk operations.
Most other stages take close to zero time, indicating that these phases currently incur no time consumption.

Ajuda e Suporte

Esta página foi útil?

comentários