Update | Description | Documentation |
Security vulnerability fixes | Redis officially announced severe security vulnerabilities in versions 6.2 and 7.2, including CVE-2024-31449, CVE-2024-31227, and CVE-2024-31228. TencentDB for Redis® has addressed and resolved these vulnerabilities. |
Update | Description | Documentation |
Adjustment of additional bandwidth policy | For newly added instances, additional bandwidth is now enabled by default. Users no longer need to manually apply for additional bandwidth when the standard bandwidth is insufficient. |
Update | Description | Documentation |
Support for Memcached Edition instances | Compatible with Memcached protocol version 1.6, this high-performance, memory-level distributed storage service is specifically designed for high-speed caching scenarios. |
Update | Description | Documentation |
Redis 7.0 | TencentDB for Redis 7.0 has been officially launched, fully compatible with community edition commands. |
Update | Description | Documentation |
Rehash maintenance time window | Added support for the rehash-maintenance-time parameter, allowing users to specify whether rehash operations can be performed during the maintenance time window. |
Update | Description | Document |
Added global replication monitoring metrics.
| Supports graphical monitoring of the command count deviation during the global replication process between the primary instance and disaster recovery instances, as well as the synchronization latency in remote synchronization. |
Update | Description | Document |
One-click connectivity checker
| If the connection to TencentDB for Redis instance fails, it is recommended to first use the one-click connectivity checker to identify the cause. |
Update | Description | Document |
Added monitoring metrics. | Adds a monitoring metric for the number of keys with expiration time set. |
Update | Description | Document |
Supported the configuration of backup file download rules | To prevent database backup data from being dragged, TencentDB for Redis allows you to download backup files from specific servers on the allowed private network. | |
Supported the selection of billing methods for clone instances | When cloning a complete new instance based on the current backup file, you can choose the pay-as-you-go billing mode. | |
Update | Description | Document |
Released Redis 6.2 | Redis 6.2 is fully released, which supports standard and cluster architectures, read/write separation, scaling without disconnection, and ultra high availability. | |
Supported exporting parameters as a file | On the Parameter Settings page in the console, you can export the parameter file of the current instance to easily view them locally. |
Update | Description | Document |
Optimized the instance list in the console | The Deployment Mode column is added in the instance list to indicate whether an instance is deployed across AZs. When exporting the instance list information, you can aggregate tags for display, which are separated by |. |
Update | Description | Document |
Added monitoring metrics | The Max Connections Utilization of Node metric is added to monitor the maximum connection utilization of all proxy nodes in an instance. |
Update | Description | Document |
Supported querying slow logs of read-only replicas | TencentDB for Redis supports slow query of read-only replica to help you troubleshoot performance problems of read-only operations. | - |
Supported smooth scale-in to the 256 MB specification | TencentDB for Redis in standard architecture supports smooth reduction of memory capacity from 1 GB or higher to 256 MB. |
Update | Description | Document |
Optimized statistical algorithm for traffic and throttling that triggers monitoring metrics | TencentDB for Redis now provides optimized statistical algorithm for inbound/outbound traffic and throttling. | - |
Supported the 256 MB specification for the standard architecture | The minimum memory specification (256 MB) is available for TencentDB for Redis 4.0 and 5.0 Memory Edition (Standard Architecture) instances in more AZs. |
Update | Description | Document |
Supported SSL encryption | TencentDB for Redis supports SSL encryption to implement encrypted data transfer. |
Update | Description | Document |
Supported minor version upgrade | TencentDB for Redis supports minor version upgrade, so that you can upgrade your instance to a newer version for more features. | |
Supported proxy upgrade | Minor versions of the TencentDB for Redis proxy are released from time to time to add more database features or fix known bugs. |
Update | Description | Document |
Upgraded the global replication feature | Multi-AZ instances can be added to a global replication group, and existing instances can be quickly upgraded to global replication instances. |
Update | Description | Document |
Supported architecture upgrade for multi-AZ deployed instances | Multi-AZ deployed instances can be upgraded from the standard architecture to cluster architecture. | |
Supported instance clone for multi-AZ deployed instances | Multi-AZ deployed instances allow you to clone a complete instance from a backup file. |
Update | Description | Document |
Supported global replication | The global replication feature allows you to add and remove instances, switch instance roles, and delete replication groups. | |
Supported custom backup retention period | You can apply for customizing the retention period of backup files through an allowlist. | |
Added the API for failure simulation | Instances in the same AZ support calling the KillMasterGroup API for failure simulation testing. | |
Added the API for master-replica switch | Instances in the same AZ support calling the ChangeReplicaToMaster API to promote a replica node (group) to a master node for master-replica switch. |
Update | Description | Document |
Supported the 256 MB memory specification for TencentDB for Redis 4.0 and 5.0 Memory Edition (Standard Architecture) | The minimum memory specification of TencentDB for Redis 4.0 and 5.0 Memory Edition (Standard Architecture) instances can be 256 MB. Currently, this is supported only in Shanghai Zone 5, Beijing Zone 6, and Guangzhou Zone 6. |
Update | Description | Document |
Supported system default templates | TencentDB for Redis now provides default parameter templates applicable to Redis 2.8 standard architecture, Redis 4.0 standard architecture, Redis 4.0 cluster architecture, Redis 5.0 standard architecture, and Redis 5.0 cluster architecture. You can view them on the parameter template page in the console. | |
Supported enabling public network access | TencentDB for Redis allows you to enable public network access in the console, so that you can connect to your TencentDB for Redis instance from a CVM instance in different VPCs over the public network. |
Update | Description | Document |
Supported parameter template | Besides the system parameter templates provided by TencentDB for Redis, you can create custom parameter templates to configure parameters in batches as needed. |
Update | Description | Document |
Supported automatic failover | TencentDB for Redis supports the automatic failover feature for proxy nodes and Redis server nodes to ensure service availability. | |
Auto-Failback | TencentDB for Redis provides the automatic failback feature for instances deployed across AZs. After the feature is enabled, if the master node is switched from the master AZ or master node group (cluster architecture) to another AZ or group after a failover occurs, it will be automatically switched back, simplifying subsequent Ops operations. | |
Manually Promoting to Master Node (Group) | For multi-AZ deployed TencentDB for Redis instances in the standard/cluster architecture, you can manually promote a replica node/node group to master node/node group. You can deploy the master node in a specified AZ/node group. | |
Reading Local Nodes Only | To reduce the access latency of a multi-AZ deployed instance, TencentDB for Redis allows you to read local nodes only. |
Update | Description | Document |
Fully supported monitoring metrics at a 5-second granularity | TencentDB for Redis now supports the 5-second monitoring granularity. After the monitoring granularity of an instance is adjusted to five seconds, the monitoring metrics, proxy, and alarm policies of the instance, and the method of viewing monitoring data in the TCOP console will change. |
Update | Description | Document |
Renamed TencentDB for Redis Hybrid Storage Edition TencentDB for Tendis | TencentDB for Redis Hybrid Storage Edition has been renamed TencentDB for Tendis. You can access TencentDB for Tendis in its own console. | |
Supported multi-AZ deployment | You can now deploy TencentDB for Redis master and replica nodes in different availability zones (AZs) of the same region. Multi-AZ deployed instances have higher availability and better disaster recovery capability than single-AZ deployed instances. |
Update | Description | Document |
Supported the 5-second granularity for monitoring data | The monitoring feature of TencentDB for Redis has been updated, with the monitoring granularity being narrowed down from one minute to five seconds. |
Update | Description | Document |
Supported version upgrade | TencentDB for Redis now supports version upgrade, so you can upgrade from a lower version of Standard Edition to a higher one, including from 2.8 to 4.0, from 2.8 to 5.0, and from 4.0 to 5.0. | |
Supported architecture upgrade | TencentDB for Redis now supports quick upgrade from standard architecture to cluster architecture to help your business expand the performance and capacity with speed. |
Update | Description | Document |
Launched TencentDB for Redis Hybrid Storage Edition | TencentDB for Redis Hybrid Storage Edition is launched. With 100% compatibility with Redis protocols, it reduces memory costs by up to 80% and delivers a hot data performance comparable with that of Memory Edition, achieving a perfect balance among compatibility, performance, and costs. |
Update | Description | Document |
Supported Redis 5.0 in DTS | You can now migrate data and upgrade instances to Redis 5.0 with DTS. |
Update | Description | Document |
Supported the service unavailable alarm feature | TencentDB for Redis now supports the service unavailable alarm feature. In addition, users can also set alarms for instance master/replica switch, read-only replica failover, and read-only replica unavailability. | |
Supported adjusting bandwidth in the console | You can now adjust instance network bandwidth on the instance details page in the Redis console. The bandwidth specifications for Cluster Edition have been fully upgraded, with shard specifications upgraded to 384 Mbps. | - |
Updated the monitoring view for Redis 2.8 | To provide more accurate monitoring information, Tencent Cloud has updated the monitoring view of Redis 2.8 instance to cluster view. If you use APIs to get monitoring data from TCOP, you need to change the view parameter from redisuuid to cluster in the code. | - |
Update | Description | Document |
Upgraded the default number of databases in an instance to 256 | For Redis 2.8, 4.0, and 5.0 Standard and Cluster Editions you purchased this month, the default number of databases in an instance has been upgraded from 16 to 256. |
Update | Description | Document |
Released Redis 5.0 | Redis 5.0 Standard and Cluster Editions have been released with all features of Redis 4.0 reserved, and support the latest STREAM data structure, new ZSET commands ZPOPMIN and ZPOPMAX , scaling without disconnection, 4 TB of storage capacity, and tens of millions of concurrent QPS. |
Update | Description | Document |
Supported access management | You can now create policies through access management which grant sub-accounts permissions to use the resources they need. | |
Supported account management in the console | TencentDB for Redis provides read-write permission control and routing policy control through the account mechanism, which helps meet the needs of business permission management in complex scenarios. Currently, only the TencentDB for Redis Community Edition (excluding Redis 2.8) supports account settings. |
Update | Description | Document |
Released monitoring 2.0 | Redis monitoring 2.0 has been released, adding more than 16 monitoring metrics, including network delay, response error and other monitoring metrics. |
Update | Description | Document |
Supported password-free access | To enable password-free access, submit a ticket. We recommend that you limit server access by using security groups after this feature is enabled. | |
Supported disabling high-risk commands online | TencentDB for Redis is now able to disable some Redis commands that may cause service instability or accidentally delete data, including flushall , flushdb , keys , hgetall , eval , evalsha , and script . | |
Supported Cluster Edition in DTS | You can now migrate self-created Redis Cluster (3.0, 3.2, and 4.0) or Codis (2.8 and 3.2) databases to TencentDB for Redis with DTS. |
Update | Description | Document |
Supported version upgrade with DTS | TencentDB for Redis instance version can now be upgraded through DTS with hot migration, which guarantees instance service continuity during the upgrade process and can update incremental data in real time. | |
Released Redis 4.0 Standard Edition | Redis 4.0 Standard Edition supports 1-master 5-replica mode, read/write separation, scaling without disconnection, and ultra high availability. |
Update | Description | Document |
Released Redis 4.0 Cluster Edition | Redis 4.0 Cluster Edition has been released and supports 4 TB of storage capacity, tens of millions of concurrent access requests, scaling without storage capacity loss, and automatic read/write separation. |
Was this page helpful?