tencent cloud

TDSQL Boundless

LOGSERVICE_META

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

Function

INFORMATION_SCHEMA.LOGSERVICE_META is used to display metadata related to LogService within an instance. This view provides key information such as basic configurations, distribution topology, and runtime parameters of LogService, which serves as a foundational view for monitoring and managing distributed log services.

Field Description

Field Name
Type
Description
sid
bigint unsigned
the unique identifier of LogService
create_ts
bigint unsigned
the timestamp when LogService was created
name
varchar(64)
the name of LogService
nodes
varchar(256)
The list of nodes where LogService is deployed, with multiple nodes separated by commas.
log_service_type
varchar(64)
the type of LogService
LOG_SERVICE_TYPE_BINLOG: Binlog CLS
other custom log service types
client_info_type
varchar(64)
the type identifier of the LogService replay node
no_use_table_history
smallint
Whether to disable the table-history replay feature (0: enable, 1: disable)
no_use_table_history_in_cache
smallint
Whether the current node has disabled the table-history replay feature (0: enable, 1: disable)
table_map
longtext
Replay table mapping, stored in JSON format.
ongoing_jobs
longtext
Current replay job execution information

Examples

tdsql > SELECT * FROM logservice_meta\\G
*************************** 1. row ***************************
sid: 29637288212299800
create_ts: 29637288212299801
name: [log_service_mysqlclient_pk_union]
nodes: node-***-001
log_service_type: LOG_SERVICE_TYPE_BINLOG
client_info_type: CLIENT_INFO_TYPE_MYSQL
no_use_table_history: 1
no_use_table_history_in_cache: 1
table_map: []
ongoing_jobs:
1 row in set (0.00 sec)

Results Interpretation
Basic Information:
LogService ID: 29637288212299800
Name: log_service_mysqlclient_pk_union
Creation Time: 29637288212299801
Distributed Topology:
Deployment node: node-***-001 (single-node deployment)
Service Type:
LogService Type: Binlog CLS
Client Type: MySQL Client
Replay Configuration:
Disabled table history replay: Yes (no_use_table_history = 1)
This node (the node executing this SQL) has disabled table history replay: Yes (no_use_table_history_in_cache = 1)
Table mapping: empty array (currently no special table mapping rules)
Active jobs: empty (currently no active replay jobs)

Ajuda e Suporte

Esta página foi útil?

comentários