- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- Expanding Instance
- Database Proxy
- Account Management
- Database Management Console (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Configuring Application Automatic Reconnection
- Impact of Modifying MySQL Master Instance Parameters
- Limits on Automatic upgrade 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
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Backup APIs
- DescribeBackupConfig
- ModifyBackupConfig
- DeleteBackup
- DescribeBackups
- DescribeBinlogs
- CreateBackup
- DescribeSlowLogs
- DescribeDataBackupOverview
- DescribeBinlogBackupOverview
- DescribeBackupSummaries
- DescribeBackupOverview
- ModifyBackupDownloadRestriction
- DescribeBackupDownloadRestriction
- ModifyLocalBinlogConfig
- DescribeLocalBinlogConfig
- Task APIs
- Security APIs
- Data Import APIs
- Parameter APIs
- Instance APIs
- DescribeDBInstanceGTID
- CloseWanService
- SwitchForUpgrade
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- ModifyDBInstanceVipVport
- ModifyDBInstanceProject
- IsolateDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- InitDBInstances
- DescribeDBInstanceRebootTime
- OpenWanService
- UpgradeDBInstance
- ModifyDBInstanceName
- DescribeDBZoneConfig
- RestartDBInstances
- OpenDBInstanceGTID
- DescribeDBSwitchRecords
- DescribeDBInstanceConfig
- ModifyAutoRenewFlag
- ModifyInstanceTag
- DescribeTagsOfInstanceIds
- ModifyTimeWindow
- DescribeTimeWindow
- DeleteTimeWindow
- AddTimeWindow
- OfflineIsolatedInstances
- ReleaseIsolatedDBInstances
- ModifyRoGroupInfo
- DescribeRoGroups
- BalanceRoGroupLoad
- DescribeDBInstanceInfo
- DescribeRoMinScale
- CreateRoInstanceIp
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- StopReplication
- StartReplication
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Database APIs
- Account APIs
- Rollback APIs
- Monitoring APIs
- Log APIs
- Database Audit APIs
- Database Proxy APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Release Notes and Announcements
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Purchase Guide
- Get Started
- Operation Guide
- Use Limits
- Operation Overview
- Instance Management and Maintenance
- Instance Upgrade
- Expanding Instance
- Database Proxy
- Account Management
- Database Management Console (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Best Practice
- Usage Specifications of TencentDB for MySQL
- Configuring Application Automatic Reconnection
- Impact of Modifying MySQL Master Instance Parameters
- Limits on Automatic upgrade 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
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Backup APIs
- DescribeBackupConfig
- ModifyBackupConfig
- DeleteBackup
- DescribeBackups
- DescribeBinlogs
- CreateBackup
- DescribeSlowLogs
- DescribeDataBackupOverview
- DescribeBinlogBackupOverview
- DescribeBackupSummaries
- DescribeBackupOverview
- ModifyBackupDownloadRestriction
- DescribeBackupDownloadRestriction
- ModifyLocalBinlogConfig
- DescribeLocalBinlogConfig
- Task APIs
- Security APIs
- Data Import APIs
- Parameter APIs
- Instance APIs
- DescribeDBInstanceGTID
- CloseWanService
- SwitchForUpgrade
- CreateDBInstanceHour
- DescribeDBInstanceCharset
- ModifyDBInstanceVipVport
- ModifyDBInstanceProject
- IsolateDBInstance
- UpgradeDBInstanceEngineVersion
- DescribeDBInstances
- InitDBInstances
- DescribeDBInstanceRebootTime
- OpenWanService
- UpgradeDBInstance
- ModifyDBInstanceName
- DescribeDBZoneConfig
- RestartDBInstances
- OpenDBInstanceGTID
- DescribeDBSwitchRecords
- DescribeDBInstanceConfig
- ModifyAutoRenewFlag
- ModifyInstanceTag
- DescribeTagsOfInstanceIds
- ModifyTimeWindow
- DescribeTimeWindow
- DeleteTimeWindow
- AddTimeWindow
- OfflineIsolatedInstances
- ReleaseIsolatedDBInstances
- ModifyRoGroupInfo
- DescribeRoGroups
- BalanceRoGroupLoad
- DescribeDBInstanceInfo
- DescribeRoMinScale
- CreateRoInstanceIp
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- StopReplication
- StartReplication
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- ModifyNameOrDescByDpId
- Database APIs
- Account APIs
- Rollback APIs
- Monitoring APIs
- Log APIs
- Database Audit APIs
- Database Proxy APIs
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
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 | Available in Instance List | Feature |
|---|---|---|---|---|
| Source instance | An instance that can be read from and written to | Yes | A source instance can mount read-only instances and disaster recovery instances to achieve read/write separation and remote disaster recovery. | |
| Read-only instance | An instance that can only be read from | Single-Node | Yes | A read-only instance cannot exist on its own. It must instead be associated with a source instance, with its data only being synced from the source instance. It must also reside in the same region as the source instance. |
| Disaster recovery instance | An instance that supports disaster recovery across AZs and regions | Two-Node | 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 more information on the creation of and notes on the read-only instance, see Creating Read-Only Instance.
- 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 Disaster Recovery Instance.
Yes
No
Was this page helpful?