Upgrading Instance Version

Last updated:2026-02-04 15:29:50

Upgrading Instance Version

Last updated: 2026-02-04 15:29:50

Overview
TencentDB for Redis® provides flexible version upgrade capabilities, helping you upgrade instances to later versions to obtain richer features and better performance. Version upgrades are divided into the following two types:
Major version upgrade: upgrades instances from the current version to a later major version. For example, you can upgrade Redis 4.0 to Redis 5.0 or Redis 6.2.
Minor version upgrade: upgrades to the latest minor version based on the current major version. Minor versions typically include improvements such as performance optimizations and bug fixes.
Support Notes
TencentDB for Redis® provides two storage engines: Redis Edition and Valkey Edition, both compatible with the Redis protocol. The support scope and limitations for version upgrades are as follows:
Storage Engine
Supported Version
Upgrade Rules
Redis Edition
4.0, 5.0, 6.2, and 7.0
Major version upgrade:
Supports upgrading from an early version to a later version: An instance can be upgraded from the current version to the next later version.
For example, Redis 4.0 to Redis 5.0, Redis 5.0 to Redis 6.2, and Redis 6.2 to Redis 7.0.
Supports cross-version upgrade: An instance can be directly upgraded to a later target version by skipping the intermediate versions.
For example, Redis 4.0 to Redis 6.2 (skipping 5.0), Redis 4.0 to Redis 7.0 (skipping 5.0 and 6.2), and Redis 5.0 to Redis 7.0 (skipping 6.2).
Does not support version downgrade: Version upgrade is a one-way operation. Once completed, the version cannot be rolled back to an earlier version.
For example, Redis 6.2 cannot be downgraded to Redis 5.0, and Redis 7.0 cannot be downgraded to Redis 6.2 or earlier versions. To use an early version, create an instance of the corresponding version.
Minor version upgrade:
The system automatically detects available minor versions for upgrades and does not support custom target versions.
Valkey Edition
8.0
Major version upgrade:
Currently, only Valkey 8.0 is supported. No later versions are available for upgrade.
Redis 7.0 and earlier versions cannot be upgraded to Valkey 8.0.
Minor version upgrade: The system automatically detects available minor versions for upgrades and does not support custom target versions.
Upgrade Process and Impact
No.
Stage
Description
Impact
1
Request resources
Request resources for the new-version instance, including proxy resources, Redis master node resources, and Redis replica node resources.
N/A.
2
Synchronize data
Synchronize full and incremental data to the new nodes.
Read/write services remain fully available, and business access remains unaffected.
3
Wait for switchover
Wait for immediate switchover or perform the switchover during the maintenance time, depending on the switchover policy you selected.
N/A.
4
Switch between versions
After the switchover conditions are met, the system sequentially upgrades the proxy component, replica nodes, and master node, and removes the old-version nodes.
During the switchover, the instance will enter a brief read-only state, typically lasting less than 1 minute. Meanwhile, client connections may experience brief disconnections lasting seconds.
5
Upgrade completed
After the upgrade is complete, the system updates the instance's version information and running status, and the instance resumes normal service.
N/A.
Pre-Upgrade Preparations
Before the version upgrade is performed, ensure that the following conditions are met:
The target instance is currently in the Running state, and no other tasks are being executed (such as capacity expansion, backup, and parameter modification).
The target version for this upgrade has been clearly identified, and its new features and compatibility requirements are understood.
The business application has automatic database reconnection capabilities and can handle brief connection interruptions during the upgrade switchover.
A manual backup of the instance is recommended before the upgrade to facilitate data recovery when necessary.
Upgrading the version
1. Log in to the TencentDB for Redis® console.
2. Above the instance list, select the region.
3. In the instance list, find the target instance.
4. Click the target Instance ID to enter the Instance Details page.
5. In the Specs Info section on the Instance Details page, click Version Upgrade after Compatible Version.
﻿
6. In the pop-up window, confirm the information of the target instance based on the following table, configure the target version, and click OK.
﻿
Parameter
Description
Instance ID
ID of the instance to be upgraded.
Instance Name
Name of the instance to be upgraded.
Compatible Version
The current compatible Redis version of the instance to be upgraded.
Architecture
Architecture information of the instance to be upgraded. Currently, version upgrade is supported only for standard architecture instances.
Memory
Memory size of the instance to be upgraded.
Version Upgrade
Select the target version in the drop-down list. You can upgrade from an earlier version to a later version or across versions.
Preview New Specs
Preview information of the instance specifications after upgrade.
Switch Time
Switch Now: The switch will be performed when the data sync is almost completed (the data left to be synced is less than 10 MB).
Switch Maintenance Time: The switch will be performed during the instance maintenance time. If the switch conditions cannot be met in the current maintenance time, the switch will be attempted in the next maintenance time. You can modify the Maintenance Window on the instance details page.
Total Fees
Fees after instance upgrade. No billing changes will be caused.
7. On the left sidebar, select Task Management, wait for the task to complete, and you can see that the version of the instance has been upgraded in the instance list.
Upgrading the minor version
1. Log in to the TencentDB for Redis® console.
2. Above the instance list, select the region.
3. In the instance list, find the target instance.
4. Click the target Instance ID to enter the Instance Details page.
5. In the Specs Info section on the Instance Details page, click Upgrade Minor Version after Compatible Version.
Note:
The system automatically detects the minor version. If the Upgrade Minor Version button is grayed out, the instance is already on the latest minor version.
﻿
6. In the Upgrade Minor Version window, confirm the instance information and the target version and select the upgrade time in Switch Time.
Switch Now: The switch will be performed when the data sync is almost completed (the data left to be synced is less than 10 MB).
Switch in Maintenance Time: The switch will be performed during the instance maintenance time. If the switch conditions cannot be met in the current maintenance time, the switch will be attempted in the next maintenance time. You can modify the Maintenance Window on the instance details page.
﻿
7. On the left sidebar, select Task Management, wait for the task to complete, and you can see that the minor version of the instance has been upgraded in the instance list.
Related APIs
API
Description
UpgradeInstanceVersion
Upgrades the version of an instance
UpgradeSmallVersion
Upgrades the minor version of an instance

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Storage Engine	Supported Version	Upgrade Rules
Redis Edition	4.0, 5.0, 6.2, and 7.0	Major version upgrade: Supports upgrading from an early version to a later version: An instance can be upgraded from the current version to the next later version. For example, Redis 4.0 to Redis 5.0, Redis 5.0 to Redis 6.2, and Redis 6.2 to Redis 7.0. Supports cross-version upgrade: An instance can be directly upgraded to a later target version by skipping the intermediate versions. For example, Redis 4.0 to Redis 6.2 (skipping 5.0), Redis 4.0 to Redis 7.0 (skipping 5.0 and 6.2), and Redis 5.0 to Redis 7.0 (skipping 6.2). Does not support version downgrade: Version upgrade is a one-way operation. Once completed, the version cannot be rolled back to an earlier version. For example, Redis 6.2 cannot be downgraded to Redis 5.0, and Redis 7.0 cannot be downgraded to Redis 6.2 or earlier versions. To use an early version, create an instance of the corresponding version. Minor version upgrade: The system automatically detects available minor versions for upgrades and does not support custom target versions.
Valkey Edition	8.0	Major version upgrade: Currently, only Valkey 8.0 is supported. No later versions are available for upgrade. Redis 7.0 and earlier versions cannot be upgraded to Valkey 8.0. Minor version upgrade: The system automatically detects available minor versions for upgrades and does not support custom target versions.

No.	Stage	Description	Impact
1	Request resources	Request resources for the new-version instance, including proxy resources, Redis master node resources, and Redis replica node resources.	N/A.
2	Synchronize data	Synchronize full and incremental data to the new nodes.	Read/write services remain fully available, and business access remains unaffected.
3	Wait for switchover	Wait for immediate switchover or perform the switchover during the maintenance time, depending on the switchover policy you selected.	N/A.
4	Switch between versions	After the switchover conditions are met, the system sequentially upgrades the proxy component, replica nodes, and master node, and removes the old-version nodes.	During the switchover, the instance will enter a brief read-only state, typically lasting less than 1 minute. Meanwhile, client connections may experience brief disconnections lasting seconds.
5	Upgrade completed	After the upgrade is complete, the system updates the instance's version information and running status, and the instance resumes normal service.	N/A.

Parameter	Description
Instance ID	ID of the instance to be upgraded.
Instance Name	Name of the instance to be upgraded.
Compatible Version	The current compatible Redis version of the instance to be upgraded.
Architecture	Architecture information of the instance to be upgraded. Currently, version upgrade is supported only for standard architecture instances.
Memory	Memory size of the instance to be upgraded.
Version Upgrade	Select the target version in the drop-down list. You can upgrade from an earlier version to a later version or across versions.
Preview New Specs	Preview information of the instance specifications after upgrade.
Switch Time	Switch Now: The switch will be performed when the data sync is almost completed (the data left to be synced is less than 10 MB). Switch Maintenance Time: The switch will be performed during the instance maintenance time. If the switch conditions cannot be met in the current maintenance time, the switch will be attempted in the next maintenance time. You can modify the Maintenance Window on the instance details page.
Total Fees	Fees after instance upgrade. No billing changes will be caused.

API	Description
UpgradeInstanceVersion	Upgrades the version of an instance
UpgradeSmallVersion	Upgrades the minor version of an instance

tencent cloud

Overview

Support Notes

Upgrade Process and Impact

Pre-Upgrade Preparations

Upgrading the version

Upgrading the minor version

Related APIs