Redis database version 6.2 reaches end of life (EOL) on April 1, 2027, for Redis Software deployments. After this date, Redis 6.2 databases will no longer receive bug fixes, security updates, or full support, regardless of the Redis Software cluster version they run on. Review the Prerequisites, follow the Upgrade planning steps, and understand What happens after EOL to prepare.
This announcement applies to the Redis database version, which has a separate lifecycle from the Redis Software cluster version.
For Redis Cloud deployments, see the separate Redis 6.2 End of Life Announcement and Upgrade Guidance for Redis Cloud.
Prerequisites
Identify your database and cluster versions.
- Check the database version in the Cluster Manager UI.
- Check the Redis Software cluster version.
- Review the bundled database version table to identify which database versions your exact cluster release supports.
- Review the cluster’s separate support lifecycle.
Prepare for application testing and maintenance.
- Test the target Redis database version in staging or pre-production.
- Review release notes and breaking changes for the target version and intervening versions.
- Back up the database before upgrading.
- Review the database upgrade prerequisites.
- Plan maintenance timing.
- Database upgrades may include brief failovers depending on topology and configuration.
- Review the Redis Software upgrade process when preparing your upgrade.
Common Scenarios and Actions
| If you are… | What to do |
| Running Redis 6.2 on a Redis Software 8.x cluster | Plan a database upgrade. Check the database version separately from the cluster version. |
| Selecting a target database version | Use Redis 7.4 as the minimum recommended target. Confirm cluster support and application compatibility. |
| Running a cluster that does not support the desired target | First upgrade to a supported cluster release that supports both Redis 6.2 and the target database version. |
| Using Lua scripts, restrictive ACLs, Streams, or Redis Stack commands | Review the relevant compatibility and breaking-change documentation before upgrading. |
| Running Active-Active databases or Redis for Kubernetes | Follow the deployment-specific upgrade procedure linked below. |
| Planning to upgrade to a cluster release that excludes Redis 6.2 | Upgrade the Redis 6.2 databases before upgrading to that cluster release. |
| Unsure about the upgrade path or sequencing | Contact your TAM or Redis Support before starting. |
Upgrade planning steps
1. Select a target database version
Redis 7.4 is the minimum recommended target database version.
- On Redis Software 7.8 or 7.22: Redis 7.4 is the default database version.
- On Redis Software 8.0.18 or later: Redis 8.6 is the recommended target if application compatibility testing allows. Confirm the bundled versions and default for your exact cluster release.
- On an older cluster that does not support the target: Plan a cluster upgrade before upgrading the database.
Redis Software cluster version 7.4 reaches EOL on November 30, 2026, and bundles database versions only through Redis 7.2. If you run that cluster version, upgrade the cluster before moving your databases to Redis 7.4 or later. Redis database version 7.4 and Redis Software cluster version 7.4 have separate lifecycles.
Direct database upgrades from Redis 6.2 to Redis 7.4 and from Redis 6.2 to Redis 8.6 are supported, provided the cluster supports both the current and target database versions and all deployment-specific prerequisites are met.
2. Plan the cluster and database upgrade sequence
Both the current database version and the target database version must be supported by the cluster when you perform the database upgrade. The cluster must also be fully upgraded and operational.
Use the following sequence:
- Check cluster compatibility. Confirm whether your current cluster supports both Redis 6.2 and your target database version.
- Upgrade the cluster if needed. Follow the supported cluster upgrade paths to reach a supported release that includes both database versions.
- Upgrade the database. Once the cluster upgrade is complete and the cluster is operational, follow the database upgrade procedure for your deployment.
- Complete any further cluster upgrade. If your final cluster target excludes Redis 6.2, upgrade the Redis 6.2 databases before proceeding to that release.
A direct database upgrade does not mean that every cluster version supports a direct cluster upgrade. Check the cluster upgrade path separately.
3. Review application compatibility and breaking changes
Review the target release and intervening database versions before upgrading. Use the Redis Software release notes and their linked database-version compatibility guidance.
| Area | What to review |
| Clients and protocols | Client-library compatibility, RESP2/RESP3 behavior, and requirements for applications using Redis Stack commands. |
| Lua scripting | Changes affecting script execution, command behavior, and script management. |
| ACLs | Changes to permissions, command categories, and ACL-related command output. |
| Error replies | Changes affecting applications that parse error messages or depend on specific error responses. |
| Streams | Changes affecting consumer groups, pending entries, and command replies. |
| Monitoring and tooling | Changes to command output or statistics consumed by dashboards and automation. |
| Deprecated commands | Whether your application uses commands deprecated in the target or intervening versions. |
For the Redis 7.2 changes, review the documented breaking changes and client prerequisites. If targeting Redis 8.6, also review the applicable Redis 7.4, 8.0, 8.2, 8.4, and 8.6 changes.
4. Follow the procedure for your deployment
| Deployment | Upgrade instructions |
| Redis Software database | Upgrade a database |
| Active-Active database (CRDB) | Upgrade Active-Active databases |
| Redis for Kubernetes | Upgrade databases on Redis for Kubernetes |
Review the Redis upgrade policy when planning cluster and database upgrades together.
What happens after EOL
Redis 6.2 databases continue running after April 1, 2027, with the following limitations:
- Redis 6.2 no longer receives security patches, CVE fixes, or bug fixes.
- Support for Redis 6.2-specific database issues is limited according to your subscription agreement. Redis Support may require a database upgrade before investigating an issue.
A Redis Software release planned for April 2027 will be the first to exclude Redis 6.2. The exact release number has not yet been confirmed.
If you still run Redis 6.2 databases, you must upgrade those databases before upgrading to a cluster release that excludes Redis 6.2. If your current cluster does not support your target database version, first move to a supported cluster release that includes both versions.
Plan to complete your Redis 6.2 database upgrades before April 1, 2027.
Get help with upgrade planning
Contact your assigned TAM or Customer Success Manager for help selecting a target version and planning the upgrade sequence. If you do not have an assigned contact, open a Redis Support ticket.
If you need more time, contact your account team or Redis Support before the EOL date to discuss your situation.
0 comments
Please sign in to leave a comment.