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

Adaptive Hotspot Lock Manager

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-02-10 11:06:00
Transaction Optimization: Self-developed System for Transaction Concurrency Control (adapted to the highly elastic RG architecture)
Adaptive Lock Manager for Hotspots: efficiently supports pessimistic locking on LSM-trees. The lock manager can split along with regions, effectively dispersing hotspot bottlenecks.
Distributed Deadlock Detection Algorithm: adopts the lowest-overhead centralized deadlock detection to ensure optimal performance.

Traditional Solutions and their Limitations

Conventional approach in the industry: using a hash lock map with a fixed number of buckets to manage waits for transaction locks.
There are two problems:
Under a highly elastic architecture, migration of transaction lock is inefficient.
Predicate locks are not supported, leading to phantom reads under the Repeatable Read (RR) isolation level.

TDStore Data Sharding Coordinated Solution

TDStore employs a lock map for sorting to support locking specific key ranges.
The lock manager is bound to region shards and can split along with regions.


도움말 및 지원

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

피드백