- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on the Rule-Based Audit Feature for Database Audit
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Some APIs with CAM Authentication Integrated
- Notice on Elimination of Some Indicators in Event Alarms
- Commercial Billing for Database Proxy
- TencentDB for MySQL Audit Upgrade
- Added Authentication APIs
- API Authentication Upgrade
- TencentDB for MySQL API 2.0 Discontinuation
- Monitoring Module Upgrade in Shanghai Region
- Monitoring Metric Optimization
- Network Architecture Upgrade
- Change of APIs for Querying the Specifications of Purchasable Database Instances
- Replacement of Certain Old Database Proxy APIs
- Added Advanced Monitoring Metrics
- Change of Calculation Formula for Memory Utilization
- Monitoring Module Upgrade and Optimization in Guangzhou and Shanghai Regions
- Monitoring Module Upgrade
- Parameter Template and Instance Purchase Process Optimization
- Binlog Will Take up Disk Space
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Stability Features
- TXRocks Engine
- 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
- Database Audit
- 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
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data Migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Practical Tutorial
- 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
- Building All-Scenario High-Availability Architecture
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- StopCpuExpand
- StartCpuExpand
- DescribeCpuExpandStrategy
- AddTimeWindow
- BalanceRoGroupLoad
- CloseWanService
- CreateRoInstanceIp
- DeleteTimeWindow
- DescribeCdbZoneConfig
- DescribeDBFeatures
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDBInstanceGTID
- DescribeDBInstanceInfo
- DescribeDBInstanceRebootTime
- DescribeDBSwitchRecords
- DescribeRoGroups
- DescribeRoMinScale
- DescribeTagsOfInstanceIds
- DescribeTimeWindow
- IsolateDBInstance
- ModifyAutoRenewFlag
- ModifyDBInstanceName
- ModifyDBInstanceProject
- ModifyDBInstanceVipVport
- ModifyInstanceTag
- ModifyNameOrDescByDpId
- ModifyRoGroupInfo
- ModifyTimeWindow
- OfflineIsolatedInstances
- OpenDBInstanceEncryption
- OpenDBInstanceGTID
- OpenWanService
- ReleaseIsolatedDBInstances
- RenewDBInstance
- RestartDBInstances
- StartReplication
- StopReplication
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- SwitchForUpgrade
- UpgradeDBInstanceEngineVersion
- CreateDBInstance
- CreateDBInstanceHour
- DescribeDBInstances
- UpgradeDBInstance
- DescribeDBZoneConfig
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- Database Proxy APIs
- AdjustCdbProxy
- AdjustCdbProxyAddress
- CloseCDBProxy
- CloseCdbProxyAddress
- CreateCdbProxy
- CreateCdbProxyAddress
- DescribeCdbProxyInfo
- DescribeProxyCustomConf
- DescribeProxySupportParam
- ModifyCdbProxyAddressDesc
- ModifyCdbProxyAddressVipAndVPort
- ModifyCdbProxyParam
- ReloadBalanceProxyNode
- SwitchCDBProxy
- UpgradeCDBProxyVersion
- Database Audit APIs
- Security APIs
- Task APIs
- Account APIs
- Backup APIs
- CreateBackup
- DeleteBackup
- DescribeBackupDownloadRestriction
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBinlogBackupOverview
- DescribeDataBackupOverview
- DescribeLocalBinlogConfig
- DescribeRemoteBackupConfig
- DescribeSlowLogs
- ModifyBackupDownloadRestriction
- ModifyLocalBinlogConfig
- ModifyRemoteBackupConfig
- DescribeBackups
- DescribeBackupConfig
- DescribeBackupDecryptionKey
- DescribeBackupEncryptionStatus
- DescribeBinlogs
- ModifyBackupConfig
- ModifyBackupEncryptionStatus
- Database APIs
- Monitoring APIs
- Log-related API
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Preset Plugin List
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on the Rule-Based Audit Feature for Database Audit
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Some APIs with CAM Authentication Integrated
- Notice on Elimination of Some Indicators in Event Alarms
- Commercial Billing for Database Proxy
- TencentDB for MySQL Audit Upgrade
- Added Authentication APIs
- API Authentication Upgrade
- TencentDB for MySQL API 2.0 Discontinuation
- Monitoring Module Upgrade in Shanghai Region
- Monitoring Metric Optimization
- Network Architecture Upgrade
- Change of APIs for Querying the Specifications of Purchasable Database Instances
- Replacement of Certain Old Database Proxy APIs
- Added Advanced Monitoring Metrics
- Change of Calculation Formula for Memory Utilization
- Monitoring Module Upgrade and Optimization in Guangzhou and Shanghai Regions
- Monitoring Module Upgrade
- Parameter Template and Instance Purchase Process Optimization
- Binlog Will Take up Disk Space
- User Tutorial
- Product Introduction
- Tencent Kernel TXSQL
- Overview
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Security Features
- Stability Features
- TXRocks Engine
- 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
- Database Audit
- 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
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Data Migration
- Monitoring and Alarms
- Operation Logs
- Tag
- Practical Tutorial
- 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
- Building All-Scenario High-Availability Architecture
- Calling MySQL APIs in Python
- White Paper
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- StopCpuExpand
- StartCpuExpand
- DescribeCpuExpandStrategy
- AddTimeWindow
- BalanceRoGroupLoad
- CloseWanService
- CreateRoInstanceIp
- DeleteTimeWindow
- DescribeCdbZoneConfig
- DescribeDBFeatures
- DescribeDBInstanceCharset
- DescribeDBInstanceConfig
- DescribeDBInstanceGTID
- DescribeDBInstanceInfo
- DescribeDBInstanceRebootTime
- DescribeDBSwitchRecords
- DescribeRoGroups
- DescribeRoMinScale
- DescribeTagsOfInstanceIds
- DescribeTimeWindow
- IsolateDBInstance
- ModifyAutoRenewFlag
- ModifyDBInstanceName
- ModifyDBInstanceProject
- ModifyDBInstanceVipVport
- ModifyInstanceTag
- ModifyNameOrDescByDpId
- ModifyRoGroupInfo
- ModifyTimeWindow
- OfflineIsolatedInstances
- OpenDBInstanceEncryption
- OpenDBInstanceGTID
- OpenWanService
- ReleaseIsolatedDBInstances
- RenewDBInstance
- RestartDBInstances
- StartReplication
- StopReplication
- SwitchDBInstanceMasterSlave
- SwitchDrInstanceToMaster
- SwitchForUpgrade
- UpgradeDBInstanceEngineVersion
- CreateDBInstance
- CreateDBInstanceHour
- DescribeDBInstances
- UpgradeDBInstance
- DescribeDBZoneConfig
- CreateDeployGroup
- DeleteDeployGroups
- DescribeDeployGroupList
- Database Proxy APIs
- AdjustCdbProxy
- AdjustCdbProxyAddress
- CloseCDBProxy
- CloseCdbProxyAddress
- CreateCdbProxy
- CreateCdbProxyAddress
- DescribeCdbProxyInfo
- DescribeProxyCustomConf
- DescribeProxySupportParam
- ModifyCdbProxyAddressDesc
- ModifyCdbProxyAddressVipAndVPort
- ModifyCdbProxyParam
- ReloadBalanceProxyNode
- SwitchCDBProxy
- UpgradeCDBProxyVersion
- Database Audit APIs
- Security APIs
- Task APIs
- Account APIs
- Backup APIs
- CreateBackup
- DeleteBackup
- DescribeBackupDownloadRestriction
- DescribeBackupOverview
- DescribeBackupSummaries
- DescribeBinlogBackupOverview
- DescribeDataBackupOverview
- DescribeLocalBinlogConfig
- DescribeRemoteBackupConfig
- DescribeSlowLogs
- ModifyBackupDownloadRestriction
- ModifyLocalBinlogConfig
- ModifyRemoteBackupConfig
- DescribeBackups
- DescribeBackupConfig
- DescribeBackupDecryptionKey
- DescribeBackupEncryptionStatus
- DescribeBinlogs
- ModifyBackupConfig
- ModifyBackupEncryptionStatus
- Database APIs
- Monitoring APIs
- Log-related API
- Data Types
- Error Codes
- FAQs
- Service Agreement
- Reference
- Glossary
- Contact Us
- Preset Plugin List
This document describes how to upgrade a TencentDB for MySQL dual-node or three-node instance to a cluster instance using the console's one-click upgrade feature.
Prerequisites
The TencentDB for MySQL dual-node or three-node instance architecture is used.
The instance is running.
Notes
After an upgrade to the cluster edition, rollback is not supported. Proceed with caution.
After an upgrade to the cluster edition, the backup files of the original instance will not be retained. If you need to keep the backup files of the original instance, download or enable the retention of the original instance in advance.
If an upgrade to the cluster edition is required, neither the original instance nor its read-only instances can have public network access enabled.
Directions
1. Log in to the TencentDB for MySQL console.
2. In the instance list, find the instance to be upgraded and click One-click Upgrade in the Billing Mode column, or check the target instance and click One-click Upgrade above the instance list.
3. In the pop-up window, select Upgrade to TencentDB for MySQL Cluster Edition and click Upgrade Now.
4. On the right side of the pop-up interface, click Change Configuration.
5. In the pop-up window, set the relevant configuration information for the cluster, and then click OK.
Parameter | Description |
AZ | It is used to select the availability zone for read-write nodes and read-only nodes. |
Disk type | It is the cloud disk by default. |
Instance specification | It is used to select the type, CPU, and memory of the instance. |
Disk | It is used to select the disk type and storage space. The storage space range is from 30 to 32,000 GB, with an increment of 10. The storage space should be at least 1.2 times the data file size and not be less than the disk size of the original instance. |
Data protection space | It is used to set data protection space, with a range from 1 to 10 GB. To ensure the recoverability of database instances, cluster instances require the setting of some space for data protection of database instances. The space cannot store data, belongs to the system protection space, and aims to prevent instances from malfunctioning when storage is full. |
6. Due to the upgrade of cluster edition alarm metrics, you need to create an alarm policy. For operations, refer to Alarm Policy.
7. After changing the configuration and selecting the alarm policy, click Upgrade Check at the bottom of the redirected interface.
8. Check items for the upgrade check are listed in the table below. If any item fails, make a necessary adjustment as reminded, and then re-run the upgrade check. Once all the check items pass the upgrade check, you can proceed to the next step.
Check Item | Check Instance Type | Description |
Audit | Primary instance Read-only instance | Check whether the original instance has database audit enabled. If so, migration is not possible. You can back up the database audit logs, disable database audit, and then upgrade to the cluster edition again. For the disabling of database audit, see Disabling Audit Service. |
Backup | Primary instance | Check whether the original instance has regular retention policy, transition-to-cold storage for backup files, or transition-to-cold storage for binlog files enabled. If so, migration is not possible. You need to disable them and try again. For more details and operations, see Backing up Databases and Configuring Transition-to-Cold Storage. |
Backup encryption | Primary instance | Check whether the original instance has backup encryption enabled. If so, migration is not possible. You need to disable it and try again. For more details and operations, see Backup Encryption. |
DR instance | Primary instance | Check whether there are disaster recovery instances under the original instance. If so, migration is not possible. You need to release the disaster recovery instances and try again. For instance releasing operations, see Terminating Instances. |
Elastic expansion | Primary instance Read-only instance | Check whether the original instance has CPU elastic expansion enabled. If so, migration is not possible. You need to disable it and try again. For more details and operations, see CPU Elastic Expansion. |
Instance status | Primary instance Read-only instance | Check whether the original instance's running status is normal. If other tasks are in progress, retry after the tasks are complete and the instance is in running state. Other abnormal status can be adjusted according to the suggested solutions. |
Single node | Primary instance Read-only instance | Check the architecture of the original instance. Only dual-node and three-node instances support one-click upgrade to the cluster edition. If the original instance adopts a single-node architecture, migration is not possible. Select an instance architecture that supports migration. |
Remote backup | Primary instance | Check whether the original instance has cross-region backup enabled. If so, migration is not possible. You can disable cross-region backup and try again. For related operations, see Cross-Region Backup. |
SSL | Primary instance Read-only instance | Check whether the original instance has SSL encryption enabled. If so, migration is not possible. You can disable SSL encryption and try again. For related operations, see Setting SSL Encryption. |
Version check | Primary instance Read-only instance | Check the kernel minor version of the original instance. Migration is possible only if the following conditions are met. For kernel minor version upgrade operations, see Upgrading Kernel Minor Version. MySQL 5.7 20230601 and later versions. MySQL 8.0 20230630 and later versions. |
TDE encryption | Primary instance | Check whether the original instance has TDE encryption enabled. If so, migration is not possible. Use an instance with TDE encryption disabled instead for an upgrade. |
9. Select the upgrade switching time. You can choose to switch during the maintenance time or upon completion of the upgrade. For the setting of maintenance time, see Setting Maintenance Time.
10. Read and check the reminder: During the instance upgrade, data will be migrated, and instance access will not be affected. After upgrade preparation is complete, an instance switch will occur, causing a momentary disconnection. Please ensure that your business has a reconnection mechanism.
11. Click Start Upgrade. You can check the upgrade progress in the Task List.
12. If you choose to switch upon upgrade completion, the original instance will be immediately upgraded to a cluster edition after data consistency verification. The upgrade is complete when the instance is in running state.
13. If you choose to switch during the maintenance time, the upgrade will be performed within the maintenance time you have set. If you want to complete the upgrade immediately, you can go to the instance list, and click Switch Now in the operation column of the target instance. After reading the precautions in the pop-up window, click Switch again. The upgrade is complete when the instance is in running state.
Note:
When you perform instance switching operation, the instance will switch to the cluster architecture.
After switching to the cluster architecture, a new read-only IP address will be generated.
After switching to the cluster architecture, the IP address of the read-write node will remain consistent with the pre-upgrade instance.
Yes
No
Was this page helpful?