tencent cloud

TDSQL Boundless

Release Notes
Product Introduction
Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
Kernel Features
Kernel Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Billing
Billing Overview
Purchase Method
Pricing Details
Renewal
Overdue Payments
Refund
Getting Started
Creating an Instance
Connect to Instances
User Guide
Data Migration
Data Subscription
Instance Management
Configuration Change
Parameter Configuration
Account Management
Security Group
Backup and Restoration
Database Auditing
Tag Management
Use Cases
Technical Evolution and Usage Practices of Online DDL
Lock Mechanism Analysis and Troubleshooting Practices
Data Intelligent Scheduling and Related Practices for Performance Optimization
TDSQL Boundless Selection Guide and Practical Tutorial
Developer Guide
Developer Guide (MySQL Compatibility Mode)
Developer Guide (HBase Compatibility Mode)
Performance Tuning
Performance Tuning Overview
SQL Tuning
DDL Tuning
Performance White Paper
Performance Overview
TPC-C Test
Sysbench Test
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Security Group APIs
Task APIs
Backup APIs
Rollback APIs
Parameter APIs
Database APIs
Data Types
Error Codes
General Reference
System Architecture
SQL Reference
Database Parameter Description
TPC-H benchmark data model reference
Error Code Information
Security and Compliance
FAQs
Agreements
Service Level Agreement
Terms of Service
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
문서TDSQL BoundlessGeneral ReferenceSQL ReferenceData DictionaryINFORMATION_SCHEMALOGSERVICE_INFO

LOGSERVICE_INFO

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-06 18:48:07

Function

INFORMATION_SCHEMA.LOGSERVICE_INFO is used to display metadata related to the LogService data unit (LogReceiver) within an instance.

Field Description

Field Name
Type
Description
rep_group_id
bigint unsigned
RG ID
sid
bigint unsigned
the unique identifier of LogService
node_name
varchar(64)
the node name where LogReceiver is deployed
node_addr
varchar(64)
the network address (IP address:Port) of the node where LogReceiver is deployed
leader_commit_index
bigint unsigned
During LogService creation, the commit index of the rep-group's Leader replica.
create_ts
bigint unsigned
the timestamp when LogReceiver was created
delete_ts
bigint unsigned
the timestamp when LogReceiver is marked for deletion (0 indicates not deleted)
is_pending
smallint
Indicates whether the LogReceiver is suspended (0: normal, 1: suspended).

Examples

tdsql> SELECT * FROM INFORMATION_SCHEMA.LOGSERVICE_INFO;
+--------------+-------------------+------------------------+---------------------+---------------------+-------------------+-------------------+------------+
| rep_group_id | sid               | node_name              | node_addr           | leader_commit_index | create_ts         | delete_ts         | is_pending |
+--------------+-------------------+------------------------+---------------------+---------------------+-------------------+-------------------+------------+
|     16048685 | 29637288212299800 | node-***-001 | ***:***  |                NULL | 29637329400367957 | 29637343912657087 |          0 |
|     32003329 | 29637288212299800 | node-***-005 | ***:*** |                NULL | 29637465950126221 | 29637466285670778 |          0 |
|     23420940 | 29637288212299800 | node-***-001 | ***:***  |                NULL | 29637391039873556 | 29637392667252366 |          0 |
+--------------+-------------------+------------------------+---------------------+---------------------+-------------------+-------------------+------------+
3 rows in set (3.74 sec)
Results Interpretation
The example shows three LogReceivers, each belonging to a different replica group.
LogReceiver is deployed on two different nodes.
All instances are in normal status (is_pending = 0).
이전 주제: LOGSERVICE_ELAPSED다음 주제: LOGSERVICE_JOBS

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백