tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary
DocumentationTencentDB for MySQLMySQL Cluster EditionIntroduction to TencentDB for MySQL Cluster Edition

Introduction to TencentDB for MySQL Cluster Edition

PDF
Focus Mode
Font Size
Last updated: 2026-01-20 15:18:17
TencentDB for MySQL supports the Cluster Edition product architecture, offering high elasticity, high performance, flexibility, and reliability. It combines the simplicity and openness of open-source cloud databases with efficient iteration advantages. The Cluster Edition provides unique features such as automatic failover, the ability to switch any replica node (read-only node) to a primary node (read-write node), read-only replica nodes, on-demand scaling of nodes by adding or deleting them, multi-availability zone disaster recovery, granular node monitoring, and cluster node topology management. It helps users tackle complex business scenarios, enabling a single database deployment to meet a variety of business requirements.

What is the Cluster Edition?

The database Cluster Edition is based on a cloud-native high availability deployment model, featuring multiple read replica database nodes. It provides both read-write and read-only access addresses. Replica databases in two-node/three-node instances serve only for high availability purposes and do not provide direct access. Considering performance and cost factors, the Cluster Edition's architecture is suitable for more complex business scenarios where there are substantial business fluctuations, large data volumes, high read performance requirements, business systems that require frequent configuration adjustment or the addition/removal of read-only instances.
In the TencentDB for MySQL Cluster Edition, async and semi-sync replication are supported. You can choose the replication mode on the purchase page, and modify it later in the console's instance details page. For more details on replication modes, see Database Instance Replication.
The storage type for the TencentDB for MySQL Cluster Edition is cloud disk, supporting Tremendous SSD, Enhanced SSD, and SSD. The cloud disk type can only be selected on the purchase page. For more details on the performance of each cloud disk, see Cloud Disk Types.

Supported regions

The current regions that support creating cluster edition instances of TencentDB for MySQL are: Guangzhou, Shanghai, Beijing, Chengdu, Singapore, and Frankfurt.

Architecture Diagram



Architecture Applications

Users can freely deploy the number of primary and replica nodes according to actual business needs to meet the most suitable database deployment method required for business operation, achieving the best balance between cost and performance.
For example, the following are some common deployment methods (representing only some scenarios).
1 Primary, 1 Replica: The read-write node is used for online business and the read-only node is used for failover preparation and lightweight read queries. It is suitable for scenarios with low to moderate availability requirements for the production environment.
1 Primary, 2 Replicas: The read-write node is used for online business, and read-only node 1 is used for online analytical reads and read-only node 2 is used for failover preparation. It is suitable for scenarios needing high availability and better flexibility.
1 Primary, Multiple Replicas: The read-write node is used for online business and multiple read-only nodes are used for distributing the load of read requests, significantly enhancing the capability to handle a high volume of read requests. It is suitable for businesses with particularly high read request demands.

Advantages

Performance Enhancement: Significant improvements from various kernel optimizations such as atomic writes, code segment optimization, and Buffer Pool pre-warming.
Read-Only Replica Nodes: Replica databases support for the configuration of read-only addresses, eliminating the need for creating inaccessible replica instances.
High Elasticity: Can quickly adjust configurations up or down based on business needs, rapidly complete scaling out, and achieve cost optimization for compute resources.
Flexibility: Can quickly add or delete read-only nodes based on business needs. A Cluster Edition instance can quickly accommodate the addition or deletion of 1 to 5 read-only nodes.
Security and Reliability: Offering both async and semi-sync replication as options, combined with multiple replica nodes, ensures business continuity by maintaining proper primary-replica sync under normal circumstances.

Billing

To understand the billing methods and items for the TencentDB for MySQL Cluster Edition, see Billing Overview.
To know the prices for the TencentDB for MySQL Cluster Edition, see Price Calculator.
For information on the TencentDB for MySQL Cluster Edition storage free space and the billing for backup beyond the free space, see Backup Space Billing.

Supported Features

The features supported by the TencentDB for MySQL Cluster Edition instances are basically the same as those of the MySQL two-node/three-node instances. For a specific feature comparison, see Feature List.
For features and operations that differentiate the TencentDB for MySQL Cluster Edition instances from the MySQL two-node/three-node instances, see Subsequent Articles in This Section.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback