tencent cloud

TDSQL Boundless

Release Notes
Product Introduction
Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
Usage specification recommendations
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
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

tdstore_enable_node_alive_detection

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-27 19:01:49

Feature Description

Controls whether to enable or disable the crash detection feature.
After this feature is enabled, each TDStore node will establish a persistent connection with all other TDStore nodes. If the persistent connection is interrupted and several retries fail, the remote TDStore node will be considered down. At this point, the downtime callback will be triggered to perform some cleanup work (such as releasing residual participant contexts).
The negative impact of enabling this feature is that, when node pressure is very high, it may theoretically cause connection interruptions, thus posing risks of killing transactions by mistake. In addition, if the number of nodes is particularly large, it will also lead to an increase in the number of connections.

Attribute Description

Required
Description
Parameter Type
BOOL
Default Value
ON
Value Range
OFF
ON
Effective Scope
GLOBAL
Restart Required
No

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan