How to upgrade the version of your Redis instance

  • Article

New versions of Redis server software are frequently released with new features, more commands, and stability improvements. Maintaining Redis instances using the latest version of Redis is a good way to ensure that you get the best possible Redis experience.

This article details how to upgrade your Redis instance to the latest version of Redis available in Azure Cache for Redis.

Important

Following the standard Redis versioning, this article only covers upgrades to the major version of Redis, not the minor or patch versions. Updates to the minor and patch versions are made automatically during the normal patching cycle each month.

Scope of availability

This table contains the information for Redis upgrades features available in each tier.

Tier Automatic Upgrade Manual Upgrade
Basic, Standard, Premium No No

Current versions

This table contains the information for which Redis version are available in each tier.

Tier Available Redis version
Basic, Standard, Premium 6.0 (GA)

How to upgrade - Basic, Standard, and Premium tiers

Currently, no upgrade is available.

Considerations before upgrading Redis versions

Each new Redis version is intended to be a seamless upgrade from previous versions with backwards-compatibilty as a design principle. However, small changes and bug fixes do occur which can cause application changes. Being conscious of these changes is always a good idea.

Client version

If you're using an outdated Redis client, new commands or Redis features can't be supported properly. We always recommend updating to the latest stable version of your Redis client, as newer versions often have stability and performance improvements as well. For more information on configuring your client library, see best practices using client libraries.

RESP3

Redis version 7.2 enables an updated Redis serialization protocol specification (RESP) called RESP3. This protocol offers richer data types and performance improvements. Using RESP3 is optional and is negotiated by the Redis client. Because some Redis clients, such as Go-Redis version 9+ and Lettuce version 6+, enable RESP3 by default, upgrading the Redis server instance to version 7.2 can produce a response with a different format. To avoid this breaking change, you can configure these clients to use RESP2 by default instead.

Breaking changes

Each version of Redis often has a few minor bug fixes that can present breaking changes. If you have concerns, we recommend reviewing the Redis 7.0 and 7.2 release notes before upgrading your Redis version:

Related content