Release Notes
Announcements
Version | Change Type | Feature Description |
5.8.20 | New Features | Supports the Valkey storage engine, providing users with more storage engine choices to meet the performance and compatibility requirements of different business scenarios. |
5.8.19 | Performance optimization | Optimize the security processing mechanism for protocol data transmission to ensure data integrity during transmission and prevent data abnormalities caused by special characters. |
5.8.18 | Performance optimization | Optimized the connection consistency check mechanism during hot version upgrades to ensure the stability of subscription-based connections during the upgrade process and reduce the impact of hot upgrades on business operations. |
5.8.17 | New Features | Added session health check capability, supporting automatic detection and cleanup of abnormal session connections to enhance session management efficiency in long-running scenarios. |
| Performance optimization | Optimized the monitoring of connection status and abnormality detection capabilities to enhance system security and connection reliability. |
5.8.16 | Performance optimization | Enhanced access routing policies to improve system security compliance. |
| | Optimized the load balancing capability for read-only replicas to enhance resource utilization and response efficiency for read requests. |
5.8.15 | Issue Fixes | Fixed compatibility issues with the seamless migration feature in extreme scenarios. |
| | Fixed resource management issues in long-running traversal operations to enhance operational stability. |
5.8.14 | Issue Fixes | Fixed communication link issues for management connections, enforcing management commands to be transmitted through internal secure channels to enhance security compliance. |
| Issue Fixes | Fixed a status synchronization issue during seamless migration in broadcast mode, ensuring data consistency across all nodes throughout the migration process. |
5.8.13 | Performance optimization | Upgraded the asynchronous refresh mechanism for routing tables, significantly reducing routing update latency and enhancing the stability and response speed of proxy services. |
| Performance optimization | Enhanced the robustness of the instance hot upgrade process to eliminate potential stability risks during upgrades between specific versions. |
5.8.12 | Issue Fixes | Resolved the issue of sporadic increased latency caused by resource contention during configuration synchronization, enhancing system operational stability. |
5.8.11 | Performance optimization | Slow logs now include request trace IDs and command type tags to help users more efficiently locate performance bottlenecks. |
| Performance optimization | Comprehensively upgraded the logging framework to enhance the stability of log writing. |
5.8.10 | Security Enhancement | Enhanced database operation security auditing capabilities by incorporating high-risk operations (such as full database scans and batch deletions) into the sensitive operation monitoring system, with automatic execution record reporting. |
5.8.9 | Issue Fixes | Enhanced the parameter validation capability for replica node queries to ensure correct request parameter formats, thereby improving system robustness. |
5.8.8 | New Features | Added multiple data operation commands, expanding data structure manipulation capabilities, including key copy (COPY), list blocking move (BLMOVE/LMOVE), sorted set range storage and difference operations (ZRANGESTORE/ZDIFF/ZUNION/ZDIFFSTORE), and more. |
5.8.1 | New Features | The shared connection feature is supported to effectively mitigate cluster overload caused by sudden surges of connections (connection storms), enhancing connection stability in high-concurrency scenarios. |
5.8.0 | New Features | Automatically disables write operations on replicas in global replication scenarios, ensuring cross-region data consistency and stability at the architectural level. |
5.7.2 | Issue Fixes | Fixed compatibility issues with the RESP3 protocol handshake command to prevent returning exception error messages. |
5.7.1 | New Features | Compatible with Redis 6.2's new commands, including key reading with expiration time (GETEX), username/password authentication, automatic claiming of message streams, and so on, enhancing protocol compatibility. |
5.7.0 | New Features | Slow log and big Key analysis logs have added client port information to facilitate precise locating of the client where the issue originates. |
| New Features | Redis 6.2 version adds support for multiple new commands (GETDEL, HELLO, and so on). |
| New Features | The cluster edition DBSIZE command supports aggregating the total number of keys across all shard nodes while retaining the ability to query individual nodes. |
| New Features | Added the multiple AZs local read feature to reduce cross-AZ access latency. |
5.6.6 | New Features | Supporting seamless migration capabilities, scaling out/in shards is imperceptible to services during transactions, message subscriptions, and blocking operations, delivering a smooth scaling experience. |
5.6.5 | Issue Fixes | Fixed issues related to the password-free access feature to ensure normal operation in passwordless connection scenarios. |
5.6.3 | New Features | Redis 6.2 adds support for commonly used commands (GETEX, username/password authentication, automatic message claiming), enhancing version compatibility. |
5.6.0 | New Features | The cluster architecture supports the WAIT command, which can wait for data synchronization to a specified number of replicas before returning, ensuring reliable data writes. |
| New Features | Supports SSL/TLS encrypted transmission to ensure secure data transfer between clients and servers. |
| Performance optimization | Optimizes cluster topology query performance and enhances the speed of obtaining node information. |
5.5.0 | New Features | The cluster architecture supports the WAIT command, ensuring the reliability of data writes. |
| | Supports the nearby access feature to reduce cross-AZ latency. |
| | The Cluster Edition supports the DBSIZE command to return the total number of keys across all shards. |
| | Slow log supports viewing client port information. |
| | Supports cluster-level batch flush operations, automatically distributed to all shard master nodes for execution. |
| | Adds monitoring metrics for large Value requests to help users identify potential large Value issues. |
| | The Cluster Edition supports global traversal capability to traverse data across all shard nodes. |
| Issue Fixes | Fixed an issue where switching databases after a transaction operation may result in an exception error. |
| | Fixed an issue where connections locked by transactions in batch request scenarios were not released in a timely manner, causing request routing exceptions. |
5.4.0 | Performance optimization | The statistical policy for P99 latency monitoring metrics has been optimized to cover all command types, providing more comprehensive and accurate performance monitoring data. |
5.2.0 | New Features | Monitoring data supports collection at a 5-second granularity, helping users observe instance performance fluctuations more precisely. |
5.1.0 | New Features | Slow logs now display the client IP address to facilitate locating the source of slow queries. |
| Issue Fixes | Fixed an issue where nested transaction calls returned exception errors. |
5.0.0 | New Features | The cluster architecture features have been significantly enhanced, improving overall performance and stability in distributed scenarios. |
Version | Change Type | Feature Description |
3.5.0 | New Features | The command analysis feature is now supported, allowing users to view performance metrics such as QPS, P99 execution latency, average execution latency, and maximum execution latency for individual commands, helping users precisely analyze business access patterns and performance bottlenecks. |
3.3.0 | Performance optimization | The granularity of system monitoring data collection supports 5-second statistics, providing a more detailed performance monitoring view. |
3.2.0 | New Features | Slow logs now display the client IP address to facilitate locating the source of slow queries. |
| Issue Fixes | Fixed an issue where nested transaction calls returned exception errors. |
フィードバック