TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
Database Instance Types
Last updated: 2024-12-30 16:56:21
A TencentDB for MySQL instance is a database environment that runs independently in Tencent Cloud. It is the basic unit for you to purchase the TencentDB for MySQL service. You can create, modify, and delete instances in the console.
Each instance is independent of each other with isolated resources. There are no CPU, memory, and IO preemption issues between instances. Each instance has its own characteristics such as database type and version, and the system has corresponding parameters to control instance behaviors.
There are three types of instances available in TencentDB for MySQL:
Instance Type | Definition | Architecture | Visible in Instance List | Feature |
Source instance | An instance that can be read from and written to | Yes | The primary instance can mount read-only instances and disaster recovery instances to achieve read-write separation and cross-region disaster recovery. Single-node architecture does not support mounting read-only instances and disaster recovery instances. Cluster Edition instances do not support mounting disaster recovery instances. | |
Read-only instance | An instance that can only be read from | Yes | A read-only instance cannot exist on its own. Instead, it must be affiliated to a source instance. Its data comes solely from syncing with the source instance, and it must reside in the same region as the source instance. | |
Disaster recovery instance | An instance that supports disaster recovery across AZs and regions | Yes | A disaster recovery instance is read-only when it syncs with a source instance. It can actively stop the sync and be promoted to a source instance for read/write access. The disaster recovery instance should reside in a different region than the source instance does. |
Reference
For the creation of and notes on two-node, three-node, and Cluster Edition read-only instances, see Creating a Read-Only Instance.
For operations of adding or removing read-only nodes in Cluster Edition, see Adding Instance Nodes and Removing Instance Nodes.
For more information on how to create and configure RO groups for read-only instances, see Managing the RO Group of Read-Only Instance.
For more information on the creation of and notes on the disaster recovery instance, see Managing Disaster Recovery Instance.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No