TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
Nonblocking DDL
Last updated: 2024-10-09 10:31:57
Feature Overview
During execution of a DML statement, if a metadata lock (MDL) is held, it will block DDL operations for the corresponding table and then block all subsequent DML statements, possibly consuming a large amount of thread resources. To prevent this case, TDSQL-C for MySQL introduces a Nonblocking DDL mechanism, protecting the system from being stalled by DDL operations waiting for MDL locks. When a DDL operation is blocked by a DML statement, subsequent DML statements will not further get blocked due to waiting for an MDL lock.
Supported Versions
The kernel version should be 3.1.15 or later for TXSQL 8.0.
Applicable Scenarios
It is applicable to scenarios where an MDL lock held during execution of a DML statement may block DDL operations for the corresponding table and then block all subsequent DML statements.
Use Instructions
Parameter Name | Dynamic | Type | Default Value | Valid Values/Value Range | Description |
txsql_nonblock_ddl | yes | bool | false | true/false | Whether to enable the Nonblocking DDL feature. |
txsql_nonblock_ddl_retry_times | yes | ulong | 1 | 0-ulong_max | Retry count after a DDL operation is blocked by an MDL lock. The default value is 1. |
txsql_nonblock_ddl_retry_interval | yes | ulong | 2 | 0-ulong_max | Retry interval after a DDL operation is blocked by an MDL lock. The default value is 2s. |
Note:
Some uncommon DDL operations may not be covered. In these scenarios, if a DDL operation is blocked by a DML statement, the system will directly return
Lock wait timeout.Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No