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 Boundless

SET PERSIST

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

Feature Description

SET PERSIST is used to persistently configure parameters by node type. This command propagates the specified parameter settings to all nodes of the same type, ensuring that configuration changes remain effective after cluster restart.

Limitations

Permission requirements: To execute this statement, you must have SYSTEM_VARIABLES_ADMIN or SUPER permissions.
Scope: Parameter changes take effect immediately and are persisted to the configuration file, remaining effective after restart.
Cluster synchronization: Parameter changes will be automatically synchronized to all nodes of the same type.
Parameter validation: The system validates parameter values. Invalid values will cause the command to fail.

Syntax

--node-type
SET PERSIST [NODE_TYPE] variable = expr [, variable = expr];
--Without specifying the node type, it is converted to SET PERSIST [NODE_TYPE] based on the node type of the node running the command, where NODE_TYPE represents the node type of that node.
SET PERSIST variable = expr [, variable = expr];

Parameter Description

Parameter
Required
Description
NODE_TYPE
Optional
Node type for persisting parameters.
Optional values:
hyper: Peer node.
storage: Storage node responsible for data storage and management.
engine: Computing engine node.
cdc: Data change capture node.
columnar: Columnar storage node.
log_only: Log node.
Parameters will only be synchronized to the corresponding types of nodes.
variable
Required
Resource parameter name.
expr
Required
Resource parameter value.

Examples

-- Check current parameter settings
tdsql3_sys_local@localhost [(none)]> SHOW VARIABLES LIKE "max_connections";
+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
| max_connections | 15750 |
+-----------------+-------+
1 row in set (0.02 sec)

-- Set the maximum number of connections for Hyper nodes
tdsql3_sys_local@localhost [(none)]> SET PERSIST HYPER max_connections = 20000;
Query OK, 0 rows affected (0.00 sec)

-- Verify parameter settings
tdsql3_sys_local@localhost [(none)]> SHOW VARIABLES LIKE "max_connections";
+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
| max_connections | 20000 |
+-----------------+-------+
1 row in set (0.01 sec)

도움말 및 지원

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

피드백