Redis Enterprise Software Updates & Release Notes

Redis Software 8!

The most performant, most secure, and richest version so far. Built for performance, scale, and reliability to power modern ML and AI applications.

Redis Software version 8.0 is now available!

Highlights

This version offers:

• Redis 8.0, 8.2, 8.4, and 8.6 feature set versions
• Performance improvements and memory reduction
• New vector set data structure
• Redis Flex revamped engine
• Redis Search upgrades
• Lag-aware availability API
• Metrics stream engine (General Availability)
• Simplified module management
• New REST API fields for database and cluster configuration
• Customer-managed certificates for internode encryption
• Smart client handoffs

Detailed release notes

For more detailed release notes, select a build version from the following table:

8.0.20-19 (May 2026)

Certificate-based authentication with LDAP group-based authorization. Amazon Linux 2023 support. API enhancements for Active-Active databases and identifying manually stopped database traffic. New search metrics.

Redis 8.6.2, 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, 6.2.13

Version changes

• POST /v1/cluster/actions/change_master REST API requests will no longer allow a node that exists but is not finished bootstrapping to become the primary node. Such requests will now return the status code 406 Not Acceptable.
• Node status now returns the actual provisional RAM and flash values even when the maximum number of shards on the node (max_redis_servers) is reached. Previously, the API returned 0 for provisional_ram_of_node and provisional_flash_of_node when a node reached its shard limit. This change affects REST API node status requests and the rladmin status nodes command's output.
• crdb_controller is enabled by default as of Redis Software version 8.0.18.

Breaking changes

• Upgrading to Redis Software version 8.0.10 through 8.0.16-29 can cause LDAP authentication to fail with "certificate signed by unknown authority" errors if your cluster currently uses LDAP authentication. This issue was fixed in Redis Software version 8.0.16-33.
• For Redis Software versions 8.0.2 through 8.0.10, LDAP filters for user_dn_query and dn_group_query strictly require parentheses to function correctly. Filters that previously worked without parentheses will no longer work after upgrading to these versions. For example, you must include the parentheses in (sAMAccountName=%u). As of version 8.0.16, this breaking change no longer applies, and both (sAMAccountName=%u) and sAMAccountName=%u are valid filters.
• Redis Software installation script changes:
  • Changed the --skip-updating-env-path option to --update-env-path when running install.sh.
  • Changed the skip_updating_env_path parameter to update_env_path in the installation answers file.

Redis database version 8 breaking changes

When new major versions of Redis Open Source change existing commands, upgrading your database to a new version can potentially break some functionality. Before you upgrade, read the provided list of breaking changes that affect Redis Software and update any applications that connect to your database to handle these changes.

ACL behavior changes

Before Redis 8, the existing ACL categories @read, @write, @dangerous, @admin, @slow, and @fast did not include commands for Redis Search and the JSON, time series, and probabilistic data structures.
Starting with Redis 8, Redis includes all Query Engine, JSON, time series, Bloom filter, cuckoo filter, top-k, count-min sketch, and t-digest commands in these existing ACL categories.

As a result:

• Existing ACL rules such as +@read +@write will allow access to more commands than in previous versions of Redis. Here are some examples:
  • A user with +@read access will be able to execute FT.SEARCH.
  • A user with +@write access will be able to execute JSON.SET.
• ACL rules such as +@all -@write will allow access to fewer commands than previous versions of Redis.
  • For example, a user with +@all -@write will not be able to execute JSON.SET.
  • Explicit inclusion of new command categories is required to maintain access. The new categories are: @search, @json, @timeseries, @bloom, @cuckoo, @topk, @cms, and @tdigest.
• ACL rules such as +@read +JSON.GET can now be simplified as +@read because JSON.GET is included in the @read category.

Note that the @all category did not change, as it always included all the commands.

Redis Search changes

The following changes affect behavior and validation in Redis Search:

• Enforces validation for LIMIT arguments (offset must be 0 if limit is 0).
• Enforces parsing rules for FT.CURSOR READ and FT.ALIASADD.
• Parentheses are now required for exponentiation precedence in APPLY expressions.
• Invalid input now returns errors instead of empty results.
• Default values revisited for reducers like AVG, COUNT, SUM, STDDEV, QUANTILE, and others.
• Updates to scoring (BM25 is now the default instead of TF-IDF).
• Improved handling of expired records, memory constraints, and malformed fields.

Reserved ports

Make sure the following ports are open before upgrading Redis Software.

Ports reserved as of Redis Software version 8.0.18:

• Port 3357 - reconciliation_tree_grpc - Internal communication

Deprecations

API deprecations

• Deprecated the policy field for bootstrap REST API requests. Use PUT /v1/cluster/policy to change cluster policies after cluster creation instead.
• Deprecated the module_args field for database REST API requests. Use the new module configuration objects search, timeseries, and probabilistic instead.
• Deprecated event_archive_cleanup_task_settings for job_scheduler REST API requests.

Redis Search deprecations

• Deprecated commands: FT.ADD, FT.SAFEADD, FT.DEL, FT.GET, FT.MGET, FT.SYNADD, FT.DROP, FT._DROPIFX, and FT.CONFIG.
• Deprecated FT.SEARCH options: GEOFILTER, FILTER, and NOSTOPWORDS.
• Deprecated vector search options: INITIAL_CAP and BLOCK_SIZE.
• Deprecated configuration parameters: WORKER_THREADS, MT_MODE, PRIVILEGED_THREADS_NUM, and GCSCANSIZE.
• Deprecated dialects: DIALECT 1, DIALECT 3, and DIALECT 4.

Internal monitoring and v1 Prometheus metrics deprecation

The existing internal monitoring engine is deprecated. We recommend transitioning to the new metrics stream engine for improved performance, enhanced integration capabilities, and modernized metrics streaming.
V1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using this guide or use new preconfigured dashboards.
As part of the transition to the metrics stream engine, some internal cluster manager alerts were deprecated in favor of external monitoring solutions. See the alerts transition plan for guidance.

Supported platforms

The following table provides a snapshot of supported platforms as of this Redis Software release. See the supported platforms reference for more details about operating system compatibility.
✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.
⚠️ Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.

Known issues

• RS196225: After upgrading to Redis Software version 8.0.x, previously working LDAP filters that use an OR clause to match multiple attributes can fail to find a unique DN for some users.
• RS193156: Active Directory LDAP authentication can fail in the Cluster Manager UI after upgrading to Redis Software version 8.0.16-33 due to an issue with LDAP TLS client certificate handling. Users previously authenticated through Active Directory can no longer sign in to the Cluster Manager UI after the upgrade.
  As a workaround, configure an LDAP client certificate using an update cluster certificates REST API request.
  PUT https://:/v1/cluster/certificates
  {
  "certificates": [
  {
  "name": "ldap_client",
  "certificate": "",
  "key": ""
  }
  ]
  }
  See Create certificates and Update certificates for more detailed instructions.
  This issue was fixed in Redis Software version 8.0.18.
• RS180550: You cannot set up SSO when the Cluster Manager UI is exposed through an IPv6-based load balancer or gateway.
  As a workaround, use an IPv4-based address for the SSO service base address, or register a DNS name that resolves to the IPv6 address.
  This issue was fixed in Redis Software version 8.0.10.
• RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors. This issue was fixed in Redis Software version 8.0.6.
• RS155734: Endpoint availability metrics do not work as expected due to a calculation error.

Known limitations

Trim ACKED not supported for Active-Active 8.4 databases

For Active-Active databases running Redis database version 8.4, the ACKED option is not supported for trimming commands.

Rolling upgrade limitation for clusters with custom or deprecated modules

Due to module handling changes introduced in Redis Software version 8.0, upgrading a cluster that contains custom or deprecated modules, such as RedisGraph and RedisGears v2, can become stuck when adding a new node to the cluster during a rolling upgrade.

Module commands limitation during Active-Active database upgrades to Redis 8.0

When upgrading an Active-Active database to Redis version 8.0, you cannot use module commands until all Active-Active database instances have been upgraded. Currently, these commands are not blocked automatically.

Redis 8.0 database cannot be created with flash

You cannot create a Redis 8.0 database with flash storage enabled. Create a Redis 8.0 database with RAM-only storage instead, or use Redis 8.2 for flash-enabled (Redis Flex) databases.

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Purge an Active-Active instance.
  Use crdb-cli crdb purge-instance instead.
• Search and export the log.

Role-based LDAP integration. Enhanced client mutual authentication. Active-Active improvements for eviction policies, migration, and the BITFIELD data type.

Redis Enterprise Software version 6.0.20 is now available! This version includes the following new features and improvements:

• A new integration for LDAP authentication and authorization into RS role-based access controls (RBAC). You can now use LDAP to authorize access to the admin console and to authorize database access.
• An enhanced clients mutual authentication mechanism, adding the ability to authenticate client connections using a Certificate Authority (CA).
• Support of Redis eviction policies on Active-Active Redis databases.
• A new migration process for Active-Active Redis database using the Active-Passive (Replica Of) mechanism.
• Support for the BITFIELD data type on Active-Active Redis databases.

And other functional and stability improvements.

Version information

Upgrade instructions

• Follow these instructions for upgrading to Redis Software 6.0.20 from Redis Software 5.6.0 and above.
  • Note that upgrades from earlier Redis Software versions are not supported.
• For Active-Active deployments, this release requires that you upgrade the CRDB featureset version.
• Upgrades of Active-Active databases to Redis Software 6.0.20, will require all their instances to run with protocol version 1 and featureset version 1 or above. Active-Active databases running on protocol version 0 and/or featureset version 0 will block the upgrade.

Product lifecycle information

• End of Life (EOL) for Redis Enterprise Software 6.0 and earlier versions, can be found here.
• EOL for Redis modules can be found here.

Deprecation Notice

• Upgrades to the next Redis Software will be enabled from version 6.0 and above.
• Support for the SASL-based LDAP mechanism was deprecated in v6.0.20. As of v6.2.12, support has been removed and the feature is obsolete.
• Starting with Redis Software version 6.0.12, Envoy replaces Nginx for internal cluster administration. Support for Nginx is considered deprecated, it will be removed in a future version.

New Features

New LDAP integration

Redis Enterprise Software integrates Lightweight Directory Access Protocol (LDAP) authentication and authorization into its role-based access controls (RBAC). You can now use LDAP to authorize access to the admin console and to manage database access.

Clients Mutual TLS authentication using a Certificate Authority (CA)

Redis Enterprise Software adds the ability to use a Certificate Authority (CA) for client authentications, allowing clients to rotate their certificates without the need to load new certificates to your database.

Redis eviction policies on Active-Active Redis databases

All Redis eviction policies are now supported on Active-Active Redis databases. You can create new Active-Active databases or edit existing ones using the UI console to enable it.

• Note that eviction is not supported yet for Active-Active Redis databases running with Auto Tiering.

Migration to an Active-Active Redis database

Redis Enterprise Software adds the ability to easily migrate your Redis database to an Active-Active Redis database using the Active-Passive (Replica Of) mechanism.

BITFIELD on Active-Active Redis databases

Redis Enterprise Software adds the ability to use the BITFIELD data type on Active-Active Redis databases. Please read more about developing for Active-Active with BITFIELD to understand the conflict resolution and limitations.

Redis modules

The following GA releases of Redis modules are bundled with Redis Software 6.0.20: (Please read the below updates for 6.0.20-97)

• RediSearch, version 2.0.6
• RedisJSON, version 1.0.7
• RedisGraph, version 2.2.14
• RedisTimeSeries, version 1.4.8
• RedisBloom, version 2.2.4

To use the updated modules with a database, you must upgrade the module on the database.

Additional capabilities

• Redis Software 6.0.20 includes open source Redis 6.0.9. For more information about Redis 6.0.9, check out the release notes.
• Redis Software 6.0.20 adds new rladmin commands for setting Ciphers suites and minimal TLS version for:
  • Control plane: setting Envoy
  • Data plane: setting the Proxy for clients connections
  • Sentinel discovery service
• Starting with Redis Software 6.0.20, new clusters will be set with minimal TLS version v1.2
  All known bugs around setting ciphers were fixed. To learn more, see Configure cipher suites.
• Starting with Redis Software 6.0.20, the syncer process was improved to automatically recover and resume synchronisation after reaching out-of-memory.
• Envoy updated and verified with multiple security headers.
• Starting with Redis Software 6.0.20:
  • The replication backlog size of new databases is allocated dynamically according to shard size.
  • The Active-Active replication backlog size of new Active-Active databases is allocated dynamically according to shard size.

Important fixes

• RS50905, RS54809, 54940 - Fix in Redis preventing missing process PID
• RS53639 - Fix to avoid stuck state machine when assigning incorrect Redis ACL with the allkeys alias or ~* and also with ~
• RS47983 - Fixed dependencies with installation using custom directories
• RS54382 - Fixed missing API documentation
• RS52433, RS53417, RS42195, RS42194, RS30526, RS46821, RS48928 - Fixed security headers for Envoy

Starting 6.0.20-69

• RS55504 - Fixed issue that caused RediSearch cursor to break.

Starting 6.0.20-97

• RS57659 - Fixed force removing an Active-Active instance which is hosted on an inaccessible cluster
• RS57315 - Fixed creation and editing of an Active-Active database with LDAP users of the new RBAC LDAP integration. This applies to UI access and REST API and does not apply to LDAP users for database access via Redis Clients
• RS57073 - Fixed a bug caused in the shard migration process which could leave unattended shards on the node
• RS56508 - Fixed backwards compatibility of client certificate when upgrading from earlier versions and using a certificate chain with Extended Key Usage extension being set to "TLS Web Server Authentication" instead of "TLS Web Client Authentication"
• RS49289 - Fixed updating the log rotation config file according to the custom config path that was set during the installation
• The bundled RedisGraph module was upgraded to v2.4.6
• The bundled RedisTimeSeries module was upgraded to v1.4.9
• The bundled RediSearch module was upgraded to v2.0.8

Known limitations

• RS81463 - A shard may crash when resharding an Active-Active database with Auto Tiering. Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.
• RS59983 - Clients may get disconnected by the proxy when one client sends an UNSUBSCRIBE command without being subscribed to any channel and disconnect before the response returns back from the server (from the proxy).
• RS60068 - The pdns might not resolve the master node after master node change. Restarting the pdns service is required in this case.
• RS61114 - Active-Active synchronization will fail in the following scenario: a new syncer connection is established AND a partial sync (psync) was initiated AND a cron job runs before the first ACK of the psync was received.
• RS55504 - Bug RS6.0.20-66 (Build #66) causes RediSearch cursor to break. Please upgrade to a higher build when running with RediSearch.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Upgrade

• Redis Software 5.4.2 introduced new Active-Active Redis Database capabilities that improve its compatibility with open source Redis. Now the string data-type in Active-Active Redis Database is implicitly and dynamically typed, just like open source Redis. To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower, you must upgrade the Active-Active Redis Database protocol.
• When you upgrade an Active-Active Redis with active AOF from Redis Software 5.4.2 or earlier to version Redis Software 5.4.4 or later:
  • If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
  • If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
• Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above by manually updating the certificates on the disk instead of updating them through the API. For help with this issue, contact Support.
• Starting from Redis Software 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.

Redis commands

• The capability of disabling specific Redis commands does not work on commands specific to Redis modules.
• CLIENT UNBLOCK command is not supported in RS 5.4 and above
• Starting from RS 5.4.2 and after upgrading the CRDB, TYPE commands for string data-type in CRDBs return "string" (OSS Redis standard).

Security

• As part of Redis commitment to security, the following Open Source Redis CVE's have been addressed in Redis Enterprise 6.0.20:
  • CVE-2021-32626 - Lua scripts can overflow the heap-based Lua stack. This has been addressed in Redis Enterprise 6.0.20-62
  • CVE-2021-32627 - Integer overflow issue with Streams. This has been addressed in Redis Enterprise 6.0.20-1
  • CVE-2021-32628 - Vulnerability in handling large ziplists. This has been addressed in Redis Enterprise 6.0.20-1
  • CVE-2021-32687 - Integer overflow issue with intsets. This has been addressed in Redis Enterprise 6.0.20-89
• The following Open Source Redis CVE's do not affect Redis Enterprise:
  • CVE-2021-32625 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis since Redis Enterprise does not implement LCS. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.4, Redis 6.0.14)
  • CVE-2021-32672 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the LUA debugger is unsupported in Redis Enterprise. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
  • CVE-2021-32675 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the proxy in Redis Enterprise does not forward unauthenticated requests. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
  • CVE-2021-32762 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the memory allocator used in Redis Enterprise is not vulnerable. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
  • CVE-2021-41099 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the proto-max-bulk-len CONFIG is blocked in Redis Enterprise. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)

Distribute synchronization across nodes for Active-Active and Active-Passive databases. Disable internal services to free memory. User accounts support password rotation. Module depdencies automatically installed. Syncer process recovery.

Redis Enterprise Software (RS) 6.0.12 is now available! This version includes the following new features and improvements:

• Synchronization can now be distributed across the nodes of Active-Active or Active-Passive databases
• You can disable several internal RS services to free up more memory
• User accounts can have multiple passwords to allow for password rotation
• Dependencies are automatically installed when you add modules to a cluster
• Envoy replaces NGINX for internal cluster administration
• Automatic recovery of the syncer process from out-of-memory (preview mode)

And other functional and stability improvements.

Version information

Upgrade instructions

• Follow these instructions for upgrading to RS 6.0.12 from RS 5.4.0 and above.
• For Active-Active deployments, this release requires that you upgrade the CRDB featureset version.

Product lifecycle information

• End of Life (EOL) for Redis Enterprise Software 6.0 and previous RS versions, can be found here.
• EOL for Redis modules can be found here.

Deprecation Notice

• Support for RS 5.4.X ended on December 31, 2020.
• Support for Red Hat Enterprise Linux 6 and Oracle Linux 6 and Ubuntu 14.04 (Trusty) operating systems platforms ended on November 30, 2020.
• This is the last RS version that supports direct upgrades from versions below 5.6.0.
• This is the last RS version that supports Active-Active protocol version below 1 and featureset version below 1.

New Features

Distributed Syncer

The syncer process now supports running in a distributed mode. This option can improve the latency for Active-Active databases with a very high throughput profile. You can configure a replicated database to use distributed synchronization so that any available proxy endpoint can manage synchronization traffic.

Disabling RS services to free memory

Redis Software users can now use the REST API to disable the following services:

• cm_server
• mdns_server
• pdns_server
• stats_archiver
• saslauthd
• crdb_coordinator
• crdb_worker

Once disabled, services are not monitored and controlled by the supervisord.

Warning: This feature can cause unintended results if the cluster relies on the disabled services. To make sure you understand the impact of disabled services, test the system in a lab environment before you deploy in production.

Support for multiple passwords

For users of Redis 6 and RS 6.0 and above, you can now add more security to your password management by maintaining multiple passwords for a user to allow seamless password rotation.

As of RS 6.0, you can assign specific data access permissions (Redis ACLs) and cluster administration permissions to users. Password rotation is especially helpful so that you can do a rolling update of the passwords in the application clients that connect to the Redis databases.

In this version, you can only configure multiple passwords using the REST API.

Redis Modules dependencies management

RedisGears GA and RedisAI GA require Redis Software to fetch and manage external dependencies. Modules declare dependencies at release time in their ramp file.

In this version of RS, these dependencies are installed by Redis Software when the module is added to the cluster. The master node downloads the required dependencies and prompts the other nodes to copy the dependencies from the master node. When all dependency requirements are satisfied, the module installation is complete. New nodes to the cluster also automatically install the dependencies.

Syncer automatic recovery from out-of-memory (Preview mode)

For Active-Active databases, the syncer process gracefully recovers from an out of memory (OOM) state.

Although Active-Active synchronization is bi-directional, in each direction we can define a source instance and a destination instance. When a destination instance (that is, the instance running the syncer process) gets OOM, the syncer process attempts to automatically recover the data synchronization when memory becomes available.

This is a configurable option and currently under preview mode. This behavior will be GA and set as default in the next RS version.

To enable the syncer automatic recovery, do these steps on each participating cluster:

1. Upgrade the featureset version to 3.
2. Enable the syncer automatic recovery using the REST API:

curl -v -k -u <username>:<password> -X PUT -H "Content-Type: application/json" -d ‘{"crdt_syncer_auto_oom_unlatch":true}’ http://<cluster_address>:8080/v1/bdbs/<database_ID>

The syncer process restarts to with automatic recovery on.

Redis modules

The following GA releases of Redis modules are bundled with RS 6.0.12:

• RediSearch, version 2.0.6
• RedisJSON, version 1.0.4
• RedisGraph, version 2.2.11
• RedisTimeSeries, version 1.4.7
• RedisBloom, version 2.2.4

To use the updated modules with a database, you must upgrade the module on the database.

Additional capabilities

• RS 6.0.12 includes open source Redis 6.0.6. For more information about Redis 6.0.6, check out the release notes.
• The bundled Nginx version was updated from version 1.16.0 to 1.18.0.
• The crdb-cli syntax to remove an instance is changed from remove-instance [--ordered|--unordered] to remove-instance [--force|--no-force].

Important fixes

• RS45627, RS47382 - Fixed bugs causing clients to disconnect when using XREAD and XREADGROUP commands in blocking mode on other clients’ connections.
• RS44656 - Fixed a bug causing TLS mode for clients connections to toggle between ‘all communication’ to ‘for crdb communication only’ when performing a global configuration change.
• RS42587 - Fixed a bug in the web UI console if the FQDN of the cluster is a substring of the FQDN of a participating cluster
• RS49404 - Fixed a bug in for upgrades with custom directories that prevent users from creating databases via the web UI console.
• RS43961 - bigkeys command fixed to handle non-printable key names
• RS45707 - Fixed a bug that caused RCP (Redis Cloud Pro) databases to reject connections while resharding the database.
• RS51144 - Fixed a bug in the syncer process that was stopping synchronization between all instances in some scenarios of network disconnection of one or more participating clusters.

with 6.0.12-58:

• RS50865 - Fixed a bug causing rladmin change master node to fail when performed after a prior successful master change.
• RS51359 - Fixed a memory leak on replica shards in Active-Active databases with replication and AOF for persistence.
• RS52363 - Updated PUB/SUB max message value size from 64KB to 512MB

Known limitations

• RS81463 - A shard may crash when resharding an Active-Active database with Auto Tiering . Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Upgrade

• RS 5.4.2 introduced new Active-Active Redis Database capabilities that improve its compatibility with open source Redis. Now the string data-type in Active-Active Redis Database is implicitly and dynamically typed, just like open source Redis. To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower, you must upgrade the Active-Active Redis Database protocol.
• When you upgrade an Active-Active Redis with active AOF from version RS 5.4.2 or earlier to version RS 5.4.4 or later:
  • If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
  • If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
• Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above by manually updating the certificates on the disk instead of updating them through the API. For assistance with this issue, contact Support.
• Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.

Redis commands

• The capability of disabling specific Redis commands does not work on commands specific to Redis modules.
• CLIENT UNBLOCK command is not supported in RS 5.4 and above
• Starting from RS 5.4.2 and after upgrading the CRDB, TYPE commands for string data-type in CRDBs return "string" (OSS Redis standard).

RediSearch 2.0 support. Improved rladmin support for module upgrades.

Redis Enterprise Software (RS) 6.0.8 is now available! This version includes the new RediSearch 2.0 module, open source Redis 6.0.5, changes the rladmin tool for upgrading modules, and includes bug fixes.

Version information

Upgrade instructions

Follow these instructions for upgrading to RS 6.0.8 from RS 5.4.0 and above. For Active-Active deployments, this release requires that you upgrade the CRDB featureset version.

End of life

End of Life (EOL) for Redis Enterprise Software 6.0 and previous RS versions, can be found here. EOL for Redis Modules can be found here.

• Support for Red Hat Enterprise Linux 6 and Oracle Linux 6 operating systems platforms will end on November 30, 2020.
• Support for Ubuntu 14.04 (Trusty Tahr) operating systems platforms will end on November 30, 2020.

New features

Open source Redis 6

RS 6.0 includes open source Redis 6.0.5. For more information about Redis 6.0.5, check out the release notes.

Upgrading Redis modules via rladmin

The rladmin CLI introduces several updates to the commands for upgrading modules. It is now easier to upgrade your modules to the latest module version. Find out more here.

Redis modules

The following GA releases of Redis Modules are bundled in RS 6.0:

• RediSearch, version 2.0 (updated)
• RedisJSON, version 1.0.4
• RedisGraph, version 2.0.19 (updated)
• RedisTimeSeries, version 1.2.7 (updated)
• RedisBloom, version 2.2.4 (updated)

To use the updated modules with a database, you must upgrade the module on the database.

Additional capabilities

• Shard level metrics have been added to the metrics_exporter and are now available from Prometheus. You can find all of the metrics here.
• RS DEB packages (for Ubuntu) and RPM packages (for RHEL) are now signed with a GPG key so customers can verify that the package is authentic and has not been tampered with. You can access the GPG on the installaion page.
• The crdb-cli history log is now being added to support packages.

Important fixes

• RS33193 - Improved log files handling in the proxy for large files.
• RS43572 - Fixed a bug causing the UI to fail when enabling SMTP STARTLS.
• RS46062 - Fixed missing metrics of Active-Active databases in Grafana.
• RS44758 - Fixed non responding button for saving a new user via the UI. With build 6.0.8-32:
• RS45627, RS47382 - Fixed bugs causing clients to disconnect when using XREAD and XREADGROUP commands in blocking mode on other clients’ connections.

Known limitations

• RS81463 - A shard may crash when resharding an Active-Active database with Auto Tiering . Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.

Active-Active databases

• RS44656 - A bug causing TLS mode for clients connections to toggle between ‘all communication’ to ‘for crdb communication only’ when performing a global configuration change. TBD
• RS51359 - Active-Active databases, using replication and Append Only File (AOF) for Database persistence, are suffering from memory leaks on replica shards, causing them to grow bigger than the master shards. Customers are advised to upgrade to RS 6.0.12 TBD. Meanwhile you can use snapshots for database persistence or restart the replica shards TBD.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Upgrade

• RS 5.4.2 introduced new Active-Active Redis Database capabilities that improve its compatibility with open source Redis. Now the string data-type in Active-Active Redis Database is implicitly and dynamically typed, just like open source Redis. To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower, you must upgrade the Active-Active Redis Database protocol.
• When you upgrade an Active-Active Redis with active AOF from version RS 5.4.2 or lower to version RS 5.4.2 or higher:
  • If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
  • If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
• Node upgrade fails if the SSL certificates were configured in version 5.0.2 or above by manually updating the certificates on the disk instead of updating them through the API. For assistance with this issue, contact Support.
• Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.

Redis commands

• The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
• Starting from RS 5.4.2 and after you upgrade an Active-Active database, TYPE commands for string data-type in Active-Active databases return "string" (OSS Redis standard).

ACL and RBAC improvements for database access. Active-Active databases support Redis Streams.

Redis Enterprise Software (RS) 6.0 is now available! This new version bundles open-source Redis 6, implements enhanced Access Control List (ACL) capabilities using Role-Based Access Control (RBAC) for database access, and adds the support of Redis Streams on Active-Active databases.

Version information

Upgrade instructions

Follow these instructions for upgrading to RS 6.0 from RS 5.4.0 and above. For Active-Active deployments, this release requires that you upgrade the CRDB featureset version.

End of life

End of Life (EOL) for Redis Enterprise Software 6.0 and previous RS versions, can be found here. EOL for Redis Modules can be found here.

• Support for Red Hat Enterprise Linux 6 and Oracle Linux 6 operating systems platforms will end on November 30, 2020.
• Support for Ubuntu 14.04 (Trusty Tahr) operating systems platforms will end on November 30, 2020.

New features

Open source Redis 6

RS 6.0 bundles latest open source Redis 6. For more information, check out the Diving into Redis 6 article.

Access control list (ACL)

Based on OSS Redis 6, RS 6.0 offers the ability to manage and control connections to your databases using users and their data access permissions in terms of commands they can execute and keys they can access.

In OSS Redis, the ACLs are managed separately per user for each database. In Redis Enterprise Software, Redis ACLs are managed for the databases at the cluster. For more information, check out the Redis Enterprise Software user management documentation.

Role-based access control (RBAC)

RS 6.0 leverages Redis ACLs to implement role-based access control that easily scale and manage data access permissions. Using roles minimizes the overhead involved in managing a cluster with many databases, multiple users, and various access control lists. For more information, check out the Redis Enterprise Software user management documentation.

Active-Active support for Redis Streams

RS 6.0 adds support for Redis streams on Active-Active geo-distributed databases using conflict-free replicated data type (CRDT). You can now use all Redis streams commands including consumer groups on Active-Active databases. To enable it, upgrade your Active-Active database featureset version to the latest (featureset version = 2) as part of the upgrade process. For more information, check out Redis Streams on Active Active databases.

Redis modules

The following GA releases of Redis Modules are bundled in RS 6.0:

• RedisBloom, version 2.2.2 (updated)
• RedisGraph, version 2.0.11 (updated)
• RedisJson, version 1.0.4
• RediSearch, version 1.6.12 (updated)
• RedisTimeSeries, version 1.2.5 (updated)

To use the updated modules with a database, you must upgrade the module on the database.

Additional capabilities

• Added the ability to configure a storage service that uses the S3 protocol. Configuration for backup location and for import and export locations of RDB files is possible. The storage service must have a valid SSL certificate. To connect to an S3-compatible storage location, run:

  rladmin cluster config s3_url <url>
  

• The crdb-cli tool was updated so it is now displaying the Active-Active database’s featureset version and the protocol version per instance.

• Added REST API and rladmin commands to modify the timeout for automatically disconnecting an inactive admin console session.

• Added no_of_expires metrics for database metrics and for shard metrics. You can access this metric from the REST API:

  no_of_expires shows the current number of volatile keys in the database.

  expired_objects shows the rate of keys expired in DB (expirations/sec).

• Added the ability to customize the welcome message on the login page in the admin console.

Important fixes

• RS39121, RS35335 - Optimized the XREAD and XREADGROUP commands so when using them in a non blocking fashion (without BLOCK keyword) they use the shared connection instead of a dedicated connection.
• RS26448 - Fixed ‘ram overhead’ metric calculation for ROF databases using AOF.
• RS31190 - Fixed a bug that causes databases with OSS Cluster API enabled to override the ‘preferred IP type’ attribute from ‘external’ to ‘internal’ (the default value).
• RS34009 - Updated the modules loading procedure for clusters with FIPS compliance enabled.
• RS38233 - Improved the Redis cleanup job handling the persistent directory.
• RS39228 - Fixed a bug in the WAIT command that in some cases was released after a longer period than requested.
• RS39749 - Fixed a bug that blocked eviction while LUA scripts were in progress.
• RS43996 - Fixed a bug when aborting an upgrade to RS 6.0.

Known limitations

• RS81463 - A shard may crash when resharding an Active-Active database with Auto Tiering. Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.

Active-Active databases

• RS51359 - Active-Active databases, using replication and Append Only File (AOF) for database persistence, are suffering from memory leaks on replica shards, causing them to grow bigger than the master shards. Customers are advised to upgrade to RS 6.0.12 TBD. Meanwhile you can use snapshots for database persistence or restart the replica shards TBD.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Upgrade

• RS 5.4.2 introduced new Active-Active Redis Database capabilities that improve its compatibility with open source Redis. Now the string data-type in Active-Active Redis Database is implicitly and dynamically typed, just like open source Redis. To use the new capabilities on nodes that are upgraded from version RS 5.4.2 or lower, you must upgrade the Active-Active Redis Database protocol.
• When you upgrade an Active-Active Redis with active AOF from version RS 5.4.2 or lower to version RS 5.4.4 or higher:
  • If replication is enabled, you must run the BGREWRITEAOF command on all replica shards after the upgrade.
  • If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
• Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.
• Dynatrace agent installed on the cluster nodes can hamper the working on Envoy process leading to failure of UI and REST API. Prior upgrading we recommend removing Dynatrace completely or try upgrading to newer versions.

Redis commands

• The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
• Starting from RS 5.4.2 and after you upgrade an Active-Active database, TYPE commands for string data-type in Active-Active databases return "string" (OSS Redis standard).

Diagnostic logging service. Call home client to send daily usage statistics to Redis. Usage reports in support packages. Revamp database API. Migration status API. Two-dimensional rack awareness. New version for actions API. Additional REST API enhancements.

Highlights

This version offers:

• Performance improvements
• Diagnostic logging service
• Call home client to send daily usage statistics to Redis
• Usage reports in support packages
• Revamp database API
• Migration status API
• Two-dimensional rack awareness
• New version for actions API
• Additional REST API enhancements

Detailed release notes

For more detailed release notes, select a build version from the following table:

7.22.0-95 (May 2025)

Bug fixes for node manager crashes after cluster upgrades and the creation of circular symlinks during cluster upgrades. Internal fixes and improvements.

Redis 7.4.2, 7.2.7, 6.2.13

Version changes

• The fully qualified domain name is now validated using the FQDN library instead of a regex during cluster creation.

Breaking changes

• Redis Software installation script changes:
  • Added --skip-updating-env-path option to install.sh.
  • Added skip_updating_env_path parameter to the installation answers file.

Reserved ports

Make sure the following ports are open before upgrading Redis Software.

Ports reserved as of Redis Software version 7.22.0:

Port 3346: cluster_api_internal - Cluster API internal port

Port 3351: cluster_watchdog_grpc_api - Cluster watchdog now supports gRPC

Port 3352: grpc_service_mesh - gRPC communication between nodes

Port 3353: local_grpc_service_mesh - Local gRPC services

Port 3354: grpc_gossip_envoy - gRPC gossip protocol communication between nodes

Port 3355: authentication_service - Authentication service internal port

Deprecations

API deprecations

• Deprecated GET /v1/bdbs//actions/optimize_shards_placement REST API request. Use PUT /v1/bdbs//actions/revamp?dry_run=true to get an optimized shard placement blueprint for a database instead.
• Deprecated the data_files option for the recovery_plan specified in POST /v2/bdbs requests. Use the new original_bdb_shards option to recover a database from the provided list of shards instead.
• Deprecated PUT /v1/cluster/update_cert REST API requests as of Redis Software version 7.22.2. Use PUT /v1/cluster/certificates to update cluster certificates instead.

Internal monitoring and v1 Prometheus metrics deprecation

The existing internal monitoring engine is deprecated. We recommend transitioning to the new metrics stream engine for improved performance, enhanced integration capabilities, and modernized metrics streaming.

V1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using this guide now, or wait to use new preconfigured dashboards when they become available in a future release.

Supported platforms

The following table provides a snapshot of supported platforms as of this Redis Software release. See the supported platforms reference for more details about operating system compatibility.

✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.

⚠️ Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.

Known issues

• RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors.
• RS155734: Endpoint availability metrics do not work as expected due to a calculation error.
• RS156391: The job_scheduler's memory usage can increase significantly when the diagnostic logging service is enabled.
• RS153589: The metrics stream engine preview reports incorrect latency metrics.

Known limitations

Upload modules before OS upgrade

If the cluster contains any databases that use modules, you must upload module packages for the target OS version to a node in the existing cluster before you upgrade the cluster's operating system.

See Upgrade a cluster's operating system for detailed upgrade instructions.

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Purge an Active-Active instance. Use crdb-cli crdb purge-instance instead.
• Search and export the log.

RedisGraph prevents upgrade to RHEL 9

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Software cluster contains a RedisGraph module, even if unused by any database. The RedisGraph module has reached end-of-life and is completely unavailable in RHEL 9.

Query results might include hash keys with lazily expired fields

If one or more fields of a hash key expire after an FT.SEARCH or FT.AGGREGATE query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.

Active defragmentation does not stop mid-key for JSON

Active defragmentation does not stop mid-key for JSON data. Large keys are defragmented in full, which might cause latency spikes.

Redis Community Edition 7.4 features

Hash field expiration. Client-side caching support. Metrics stream engine preview. New APIs to check database availability, rebalance shards, fail over shards, and control database traffic. Cluster Manager UI enhancements for node actions, database tags, and database configuration. User manager role. Log rotation based on both size and time. Module management enhancements. Configurable minimum password length. Configurable license expiration alert threshold.

This version offers

• Redis Community Edition 7.4 features
• Hash field expiration
• Client-side caching support
• Metrics stream engine preview
• New APIs to check database availability, rebalance shards, fail over shards, and control database traffic
• Cluster Manager UI enhancements for node actions, database tags, and database configuration
• User manager role
• Log rotation based on both size and time
• Module management enhancements
• Configurable minimum password length
• Configurable license expiration alert threshold

Detailed release notes

For more detailed release notes, select a build version from the following table:

Version (Release date) | Major changes | Redis Open Source compatibility
7.8.6-263 (May 2026) | Internal fixes and improvements. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-260 (April 2026) | Internal fixes and improvements. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-256 (March 2026) | Internal fixes and improvements. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-253 (February 2026) | Bug fixes for database recovery and modifying databases in the Cluster Manager UI. Internal fixes and improvements. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-207 (September 2025) | Enhanced timeout diagnostics and logging when restarting shards. Bug fix for viewing shard memory usage metrics in the Cluster Manager UI. Internal fixes and improvements. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-152 (August 2025) | Bug fixes for Active-Active syncing, event log entries for configuration changes made by LDAP users, LDAP mapping visibility in the Cluster Manager UI, database max_connections setting, and memory leaks when using Active-Active databases in Kubernetes. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-119 (June 2025) | Bug fixes for user password management REST API requests, maintenance mode snapshot cleanup, and rlec_supervisor file permissions. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-95 (May 2025) | Performance improvements for the Cluster Manager UI's nodes screen. Bug fix for slowness and intermittent failures in the Cluster Manager UI, rladmin, and rlcheck after upgrading large clusters to version 7.8.4. Bug fix for an issue that could cause inconsistent memory settings across shards and out-of-memory errors. Bug fix for an issue where certain processes might not terminate as expected during cluster upgrades due to timeouts. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-60 (April 2025) | Bug fixes for an LDAP connection issue caused by setting LDAP bind credentials that include < in the Cluster Manager UI and an issue where migrated shards can appear stuck on multiple nodes. Deprecated required_version in the bootstrap cluster API. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-36 (April 2025) | Bug fixes, including a fix for an issue where new workers might use an outdated certificate after a certificate update. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.6-13 (March 2025) | Configurable hashing algorithm for user passwords. Dry run option to validate REST API requests for users and roles. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.4-95 (March 2025) | Bug fixes for server restart failures during upgrades, connectivity checks for optional services, swapped shard status and watchdog status values in rladmin, process exporter crashes, and a syncer issue for Active-Active databases that have the OSS Cluster API enabled. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.4-66 (February 2025) | Ubuntu 22 support. Bug fixes for crashes, unexpected restarts, and incorrect type for the automatically calculated replica buffer. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.4-18 (December 2024) | Certificate-based authentication for the REST API. Dry run option to validate Redis ACL REST API requests. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.2-60 (December 2024) | Bug fixes, including a fix for a RHEL 8 OpenSSL dependency issue that caused frequent restarts of the cm_server and prevented access to the Redis Software Cluster Manager UI after upgrading to Redis Software version 7.8.2-34. | Redis 7.4.0, 7.2.4, 6.2.13
7.8.2-34 (November 2024) | Redis Community Edition 7.4 features. Hash field expiration. Client-side caching support. Metrics stream engine preview. New APIs to check database availability, rebalance shards, fail over shards, and control database traffic. Cluster Manager UI enhancements for node actions, database tags, and database configuration. User manager role. Log rotation based on both size and time. Module management enhancements. Configurable minimum password length. Configurable license expiration alert threshold. | Redis 7.4.0, 7.2.4, 6.2.13

Version changes

• Added validation to verify the LDAP server URI contains a host and port when updating LDAP configuration.
• The value of the oss_sharding API field had no effect in previous versions of Redis Software. However, oss_sharding is now set to take effect as part of future plans. Until further notice, set this field to false to avoid unintended impacts.

Breaking changes

Redis Software version 7.8.2 introduces the following breaking changes:

• When you upgrade a database, the upgrade process also attempts to upgrade database modules by default.
  • The default value of latest_with_modules has changed to true.
  • rladmin upgrade db will always upgrade the database's modules.
  • When you upgrade a database using the REST API, you can set "latest_with_modules": false in the request body to prevent module upgrades.
• Authentication method changes for /v1/users/password REST API requests.
  • PUT, POST, and DELETE methods require users to include their usernames and a current password in the authentication header to change their password lists. If the authentication header is not provided, the response status will be 401 Unauthorized.
  • /v1/users/password requests change the password list of the user who provides their credentials in the authorization header when sending the requests.
  • PUT and POST requests will ignore username and old_password parameters provided in the request body.
  • DELETE requests will ignore the username parameter provided in the request body.
• Authentication method changes for POST /v1/users/authorize REST API requests.
  • The POST method requires users to include their usernames and a current password in the authentication header to generate a JSON Web Token.
  • POST /v1/users/authorize generates a token for the user who provides their credentials in the authorization header when sending the requests.
  • POST requests will ignore username and password parameters provided in the request body.

Redis database version 7.4 breaking changes

When new major versions of Redis Community Edition change existing commands, upgrading your database to a new version can potentially break some functionality. Before you upgrade, read the provided list of breaking changes that affect Redis Software and update any applications that connect to your database to handle these changes.

Security behavior changes

• Lua: LRU eviction for scripts generated with EVAL.

Other general behavior changes

• Lua: allocate VM code with jemalloc instead of libc and count it as used memory.
• ACL LOAD: do not disconnect all clients.

Product lifecycle updates

End-of-life policy extension

The end-of-life policy for Redis Software versions 6.2 and later has been extended to 24 months after the formal release of the subsequent major version. For the updated end-of-life schedule, see the Redis Software product lifecycle.

Supported upgrade paths

Redis Software versions 6.2.4 and 6.2.8 do not support direct upgrades beyond version 7.4.x. Versions 6.2.10, 6.2.12, and 6.2.18 are part of the upgrade path. To upgrade from 6.2.4 or 6.2.8 to versions later than 7.4.x, an intermediate upgrade is required.
The next major Redis Software release will still bundle Redis database version 6.2 and allow database upgrades from Redis database version 6.2 to 7.x.
See the Redis Software product lifecycle for more information about release numbers.

End of triggers and functions preview

The triggers and functions (RedisGears) preview has been discontinued.

• Commands such as TFCALL, TFCALLASYNC, and TFUNCTION will be deprecated and will return error messages.
• Any JavaScript functions stored in Redis will be removed.
• JavaScript-based triggers will be blocked.
• Lua functions and scripts will not be affected.
  If your database currently uses triggers and functions, you need to:

1. Adjust your applications to accommodate these changes.
2. Delete all triggers and functions libraries from your existing database:
   • Run TFUNCTION LIST.
   • Copy all library names.
   • Run TFUNCTION DELETE for each library in the list.
     If any triggers and functions libraries remain in the database, the RDB snapshot won't load on a cluster without RedisGears.
3. Migrate your database to a new database without the RedisGears module.

Reserved ports

Make sure the following ports are open before upgrading Redis Software.
Ports reserved as of Redis Software version 7.8.2:

Port | Process name | Usage
3347 | cert_exporter | Reports cluster certificate metrics
3348 | process_exporter | Reports process metrics for DMC and Redis processes
3349 | cluster_wd_exporter | Reports cluster watchdog metrics
3350 | db_controller | Internode communication
9091 | node_exporter | Reports host node metrics related to CPU, memory, disk, and more
9125 | statsd_exporter | Reports push metrics related to the DMC and syncer, and some cluster and node metrics

See Ports and port ranges used by Redis Software for a complete list.

Deprecations

API deprecations

• Deprecated background_op field from BDB REST API object. Use GET /v1/actions/bdb/ instead.
• Deprecated the following fields for upgrade database REST API requests:
  • keep_redis_version; use redis_version instead
  • current_module; use new_module_args instead
  • new_module; use new_module_args instead
• Deprecated the following module_list fields for create database REST API requests:
  • module_id; use module_name instead
  • semantic_version; use module_args instead
• min_redis_version is only relevant to Redis database versions earlier than 7.4 and is replaced with compatible_redis_version in module REST API responses.
• Deprecated the rladmin upgrade modules command. Use rladmin upgrade db instead.
• Deprecated POST /v1/modules/upgrade/bdb/ REST API request. Use POST /v1/bdbs//upgrade to upgrade modules instead.
• Deprecated the required_version option for the bootstrap cluster API.

V1 Prometheus metrics deprecation

V1 Prometheus metrics are deprecated but still available. To transition to the new metrics stream engine, either migrate your existing dashboards using Prometheus v1 metrics and equivalent v2 PromQL now, or wait to use new preconfigured dashboards when they become available in a future release.

Download center modules deprecation

New Redis modules will not be available for download from the Redis download center.

Legacy UI not supported

The legacy UI was deprecated in favor of the new Cluster Manager UI in Redis Software version 7.2.4 and is no longer supported as of Redis Software version 7.8.2.

Redis 6.0 databases not supported

Redis database version 6.0 was deprecated in Redis Software version 7.4.2 and is no longer supported as of Redis Software version 7.8.2.
To prepare for the removal of Redis database version 6.0 before you upgrade to Redis Software version 7.8.2:

• For Redis Software 6.2.* clusters:
  1. Set the Redis upgrade policy to latest:
     rladmin tune cluster redis_upgrade_policy latest
  2. Upgrade Redis 6.0 databases to Redis 6.2. See the Redis 6.2 release notes for the list of changes.
• For Redis Software 7.2.4 and 7.4.2 clusters, upgrade Redis 6.0 databases to Redis 7.2. Before you upgrade your databases, see the list of Redis 7.2 breaking changes and update any applications that connect to your database to handle these changes.

Ubuntu 18.04 not supported

Ubuntu 18.04 was deprecated in Redis Software version 7.2.4 and is no longer supported as of Redis Software version 7.8.2.

Upcoming changes

Default image change for Redis Software containers

Starting with version 7.8, Redis Software containers with the image tag x.y.z-build will be based on RHEL instead of Ubuntu.
This change will only affect you if you use containers outside the official Redis Enterprise for Kubernetes product and use Ubuntu-specific commands.
To use Ubuntu-based images after this change, you can specify the operating system suffix in the image tag. For example, use the image tag 7.4.2-216.focal instead of 7.4.2-216.

Supported platforms

The following table provides a snapshot of supported platforms as of this Redis Software release. See the supported platforms reference for more details about operating system compatibility.
✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules.
⚠️ Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release.

Known issues

• RS131972: Creating an ACL that contains a line break in the Cluster Manager UI can cause shard migration to fail due to ACL errors.
• RS151990: For RHEL 8 and RHEL 9 clusters, importing an RDB file can fail with the exception: Failed to import rdb file: general-error.
  As a workaround:
  1. On each cluster node, run: sudo dnf install boost-program-options
  2. Verify that libboost_program_options.so.1.75.0 points to a path to confirm the installation succeeded: ldd /opt/redislabs/bin/rl_rdbloader
     This issue was fixed in Redis Software version 7.8.6-36.

Known limitations

Upload modules before OS upgrade

If the cluster contains any databases that use modules, you must upload module packages for the target OS version to a node in the existing cluster before you upgrade the cluster's operating system.
See Upgrade a cluster's operating system for detailed upgrade instructions.

New Cluster Manager UI limitations

The following legacy UI features are not yet available in the new Cluster Manager UI:

• Purge an Active-Active instance. Use crdb-cli crdb purge-instance instead.
• Search and export the log.

RedisGraph prevents upgrade to RHEL 9

You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Software cluster contains a RedisGraph module, even if unused by any database. The RedisGraph module has reached end-of-life and is completely unavailable in RHEL 9.

Query results might include hash keys with lazily expired fields

If one or more fields of a hash key expire after an FT.SEARCH or FT.AGGREGATE query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.

New Cluster Manager UI enhancements, including Active-Active database management. Full TLS 1.3 support. Automatic recovery configuration. Full IPv6 support, including for internal traffic. Maintenance mode enhancements. Module management enhancements. RHEL 9 support.

This version offers

• New Cluster Manager UI enhancements, including Active-Active database management
• Full TLS 1.3 support
• Automatic recovery configuration
• Full IPv6 support, including for internal traffic
• Maintenance mode enhancements
• Module management enhancements
• RHEL 7 and Oracle Linux 7, which were previously deprecated, are no longer supported
• RHEL 9 support

Detailed release notes

For more detailed release notes, select a build version from the following table:

7.4.6-279 (February 2026): Internal fixes and improvements. Compatible with Redis 7.2.4, 6.2.13, 6.0.20

Product lifecycle updates

The end-of-life policy for Redis Enterprise Software versions 6.2 and later has been extended to 24 months after the formal release of the subsequent major version.

Supported upgrade paths

Redis Enterprise Software versions 6.2.4 and 6.2.8 do not support direct upgrades beyond version 7.4.x. Versions 6.2.10, 6.2.12, and 6.2.18 are part of the upgrade path. To upgrade from 6.2.4 or 6.2.8 to versions later than 7.4.x, an intermediate upgrade is required.

Deprecations

• The replica HA cluster policy is deprecated.
• The maintenance mode option keep_slave_shards is deprecated in rladmin and the REST API. Use evict_ha_replica and evict_active_active_replica instead.
• /v1/debuginfo REST API paths are deprecated. Use the new paths /v1/cluster/debuginfo, /v1/nodes/debuginfo, and /v1/bdbs/debuginfo instead.

Legacy UI deprecation

The legacy UI is deprecated in favor of the new Cluster Manager UI and will be removed in a future release.

Redis 6.0 database deprecation

Redis database version 6.0 is deprecated as of Redis Enterprise Software version 7.4.2 and will be removed in a future release.

End of triggers and functions preview

The triggers and functions (RedisGears) preview has been discontinued.

• Commands such as TFCALL, TFCALLASYNC, and TFUNCTION will be deprecated and will return error messages.
• Any JavaScript functions stored in Redis will be removed.
• JavaScript-based triggers will be blocked.
• Lua functions and scripts will not be affected.

RedisGraph end of life

Redis has announced the end of life for RedisGraph. Redis will continue to support all RedisGraph customers, including releasing patch versions until January 31, 2025.

Operating system retirements

RHEL 7 and Oracle Linux 7 are no longer supported as of Redis Enterprise Software 7.4.2.

Security retirements

• The RC4 encryption cipher is no longer supported.
• The 3DES encryption cipher is no longer supported.
• TLS 1.0 and TLS 1.1 connections are no longer supported.

Upcoming changes

Default image change for Redis Enterprise Software containers

Starting with the next major version, Redis Enterprise Software containers with the image tag x.y.z-build will be based on RHEL instead of Ubuntu.

Supported platforms

The release supports various platforms including RHEL 9, RHEL 8, Ubuntu 22.04, Amazon Linux 2, Kubernetes, and Docker with details on support and deprecation warnings.

Known issues

• RS131972: Creating an ACL with a line break can cause shard migration to fail.
• RS61676: Full chain certificate update fails if any certificate lacks a Common Name.
• RS119958: debuginfo script fails with error if too many RocksDB log files.
• RS122570: REST API POST /crdbs responds with confusing error if requested module is missing.
• RS123142: Active-Active setup issue causing missing keys and potential data loss.

Known limitations

New Cluster Manager UI limitations include missing features like removing a node, purging an Active-Active instance, and searching/exporting logs.

OpenSSL compatibility issue for 7.4.2 modules on Amazon Linux 2

Redis Enterprise Software version 7.4.2-54 is not fully supported on Amazon Linux 2 clusters with certain modules due to OpenSSL 1.1 compatibility issues.

RedisGraph prevents upgrade to RHEL 9

Clusters containing RedisGraph module cannot upgrade to RHEL 9.

Cannot create Redis v6.x Active-Active databases with modules

This limitation was fixed in Redis Enterprise Software version 7.4.2-104.

Firewalld configuration fails on RHEL 9 due to file permissions

Workaround steps provided; fixed in Redis Enterprise Software version 7.4.2-129.

Highlights

This version offers:

• Redis 7.0 and 7.2 features
• Auto Tiering (enhanced successor to Redis on Flash)
• RESP3 support
• Sharded pub/sub
• A preview of the new Cluster Manager UI (admin console)
• Redis Stack 7.2 features
• Three Redis database versions: 7.2, 6.2, 6.0
• License file structure updates
• Redis ACL selectors and enhanced key-based permissions
• New INFO fields
• Log rotation enhancements
• Multi-OS upgrade support for clusters with modules

Detailed release notes

For more detailed release notes, select a build version from the following table:

7.2.4-153 (April 2026): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-138 (September 2025): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-132 (June 2025): Bug fix for mismatched key counts in Active-Active databases after cluster recovery. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-130 (May 2025): Retry mechanism for listener creation on database ports. Bug fix for Lua out-of-memory errors preventing scripts from running Redis commands. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-122 (March 2025): Internal fixes and improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-109 (May 2024): Bug fixes. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-105 (February 2024): LDAP authentication timeout is configurable using the REST API. RHEL 8.9 support. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-92 (November 2023): New Cluster Manager UI enhancements - LDAP configuration improvements. New capability_name field added to module REST API object. Automatic removal of deprecated, predefined roles and ACLs upon cluster upgrade, unless they are associated with any users or databases. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-72 (October 2023): New Cluster Manager UI enhancements - database upgrade configuration, database defaults, user lockout parameters, and TLS configuration improvements. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-64 (September 2023): Improved cluster recovery with manually uploaded modules. Support package contains supervisorctl status. Configure port range using rladmin and REST API. License API returns the number of used shards (RAM & flash). Compatible with Redis 7.2.0, 6.2.13, 6.0.20

7.2.4-52 (August 2023): Redis 7.0 and 7.2 features. Auto Tiering (enhanced successor to Redis on Flash). RESP3 support. Sharded pub/sub. Preview of the new Cluster Manager UI. Redis Stack 7.2 features. Three Redis database versions. License file structure updates. Redis ACL selectors and enhanced key-based permissions. New INFO fields. Log rotation enhancements. Multi-OS upgrade support for clusters with modules. Compatible with Redis 7.2.0, 6.2.13, 6.0.20

Additional notes include breaking changes, deprecations, command and API deprecations, access control deprecations, legacy UI deprecation, RedisGraph end-of-life announcement, platform support and deprecations, known issues and limitations, and module-related limitations and fixes.

Pub/sub ACLs & default permissions. Validate client certificates by subject attributes. Ubuntu 20.04 support.

Redis Enterprise Software version 6.4.2 is now available!

This version offers:

• Extended validation of client certificates via mTLS (mutual TLS) full subject support
• Support for default restrictive permissions when using publish/subscribe commands and access control lists (ACLs)
• Enhanced TLS performance when Redis returns large arrays in responses
• Compatibility with open source Redis 6.2.7 and 6.2.10.
• Additional enhancements and bug fixes

Detailed release notes

For more detailed release notes, select a build version from the following table:

6.4.2-131 (September 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-127 (June 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-121 (March 2025): Internal fixes and improvements. Compatible with Redis 6.2.10, 6.0.17
6.4.2-115 (Oct 2024): RediSearch v2.6.23. RedisBloom v2.4.12. RedisTimeSeries v1.8.15. Compatible with Redis 6.2.10, 6.0.17
6.4.2-110 (May 2024): RedisGraph v2.10.15. RedisBloom v2.4.8. Bug fixes. Compatible with Redis 6.2.10, 6.0.17
6.4.2-103 (October 2023): RHEL 8.8 support. RediSearch v2.6.12. RedisGraph v2.10.12. RedisTimeSeries v1.8.11 Log when CCS schema changes. Bug fixes. Compatible with Redis 6.2.10, 6.0.17
6.4.2-94 (July 2023): Look-ahead mechanism for planner attempts. Package OS compatibility validation. Compatible with Redis 6.2.10, 6.0.17
6.4.2-81 (June 2023): Email alerts for database backup failures and replica high availability shard relocation failures. Compatible with Redis 6.2.10, 6.0.17
6.4.2-69 (May 2023): Amazon Linux 2 support. Configure envoy ports using rladmin. Added option to avoid specific nodes when using the optimized shards placement API. Added failure_detection_sensitivity to replace watchdog_profile. Compatible with Redis 6.2.10, 6.0.17
6.4.2-61 (April 2023): Amazon Linux 2 support. Fixed known limitations for custom installation on RHEL 7 and RHEL 8, running rl_rdbconvert manually, and resharding rack-aware databases with no replication. Compatible with Redis 6.2.10, 6.0.17
6.4.2-43 (March 2023): Ubuntu 20.04 support. Safe node removal. Allow gossip_envoy port configuration. Compatible with Redis 6.2.10, 6.0.17
6.4.2-30 (February 2023): Pub/sub ACLs & default permissions. Validate client certificates by subject attributes. Compatible with Redis 6.2.7, 6.0.16

Database auditing. Private key encryption. Active-Active database support for MEMORY USAGE command.

Redis Enterprise Software version 6.2.18 is now available!

This version of Redis Enterprise Software offers:

• RedisJSON on Active-Active General Availability
• Database connection auditing
• Private key encryption
• Active-Active support for memory usage command
• crdb-cli improvements
• Compatibility with open source Redis v6.2.6
• Additional enhancements and fixes

Detailed release notes

For more detailed release notes, select a build version from the following table:

Version (Release date) | Major changes | OSS Redis compatibility

6.2.18-70 (January 2023) | New script to generate new self-signed certificates for renewal. Improved logs. Deactivate alert_mgr using rladmin. | Redis 6.2.6, 6.0

6.2.18-65 (December 2022) | Added To field to test email server alerts. New flag to skip cluster resource validation during imports. Improved error messages. | Redis 6.2.6, 6.0

6.2.18-58 (November 2022) | UI support for custom REST API port. Added info level for troubleshooting redis_mgr. | Redis 6.2.6, 6.0

6.2.18-49 (October 2022) | New REST API endpoint to check whether a node is a primary or a replica. Added metrics to track certificate expiration time. | Redis 6.2.6, 6.0

6.2.18-43 (September 2022) | Database auditing. Private key encryption. Active-Active database support for MEMORY USAGE command. Improvements to crdb-cli. | Redis 6.2.6, 6.0

Deprecations

Active-Active database persistence

The snapshot option for data persistence on Active-Active databases will be deprecated in a future version of Redis Enterprise Software. If you have an Active-Active database using snapshot persistence, switch to AOF persistence. Use crdb-cli to do so:

crdb-cli crdb update --crdb-guid <CRDB_GUID> --default-db-config '{"data_persistence": "aof", "aof_policy":"appendfsync-every-sec"}'

TLS 1.0 and TLS 1.1

TLS 1.0 and TLS 1.1 connections are considered deprecated in favor of TLS 1.2 or later.
Please verify that all clients, apps, and connections support TLS 1.2. Support for the earlier protocols will be removed in a future release.
Certain operating systems, such as RHEL 8, have removed support for the earlier protocols. Redis Enterprise Software does not support connection protocols that are not supported by the underlying operating system.

3DES encryption cipher

The 3DES encryption cipher is considered deprecated in favor of stronger ciphers like AES.
Please verify that all clients, apps, and connections support the AES cipher. Support for 3DES will be removed in a future release.
Certain operating systems, such as RHEL 8, have already removed support for 3DES. Redis Enterprise Software cannot support cipher suites that are not supported by the underlying operating system.

Known limitations

Feature limitations

• RS54131 Running the QUIT command on a TLS connected database closes connection and does not return a +OK reply
• An intermittent issue can occur where a CRDB process becomes stuck in a restart loop. If this issue occurs while upgrading to Redis Enterprise Software version 6.2.18, please upgrade to the latest version 6.4.2-69 or contact support.
• RS40641 - API requests are redirected to an internal IP in case the request arrives from a node which is not the master. To avoid this issue, use rladmin cluster config to configure handle_redirects or handle_metrics_redirects.
• RS51144, RS102128 - Active-Active: To start successfully, the syncer (crdt-syncer) must connect to all sources. In multi-cluster configurations (more than 2 A-A clusters participating), in some cases, if one or more of the clusters is not available, A-A replication will be down.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.
As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Upgrade limitations

Before you upgrade a cluster that hosts Active-Active databases with modules to v6.2.18, perform the following steps:

1. Use crdb-cli to verify that the modules (modules) and their versions (in module_list) are as they appear in the database configuration and in the default database configuration:

crdb-cli crdb get --crdb-guid <crdb-guid>

1. From the admin console's redis modules tab, validate that these modules with their specific versions are loaded to the cluster.
2. If one or more of the modules/versions are missing or if you need help, contact Redis support before taking additional steps.

OCSP Support. Password & session configuration changes. RHEL 8.6 support.

Redis Enterprise Software version 6.2.12 is now available!

This version of Redis Enterprise Software offers:

• OCSP stapling of the server proxy certificate
• Password and session configuration settings via the admin console
• Compatibility with open source Redis v6.2.6
• Support for Red Hat Enterprise Linux (RHEL) v8.6
• Additional enhancements and fixes

The following table shows the MD5 checksums for the available packages.

Features and enhancements

• Server side OCSP Stapling

Online Certificate Status Protocol (OCSP) helps verify the status of certificates managed by a third-party certificate authority (CA). It tells you whether certificates are valid, revoked, or unknown. Redis Enterprise Software v6.2.12 implements OCSP stapling, which allows clients to validate the status of a server proxy certificate. When OCSP is enabled, the Redis Enterprise server regularly polls the CA OCSP responder to determine a certificate's status. The response is cached until the next polling attempt; the cached value is served to clients during the TLS handshake. To learn more, see Enable OCSP stapling.

• Session and security attributes in the admin console

You can now use the admin console to configure password complexity rules, user login lockout, and session timeout.

• Mount point import enhancement

When importing data, Redis Enterprise copies files to a temporary directory on the node. For mount point import sources only, Redis Enterprise now reads files directly from the mount point. Because this import method does not copy files to a temporary directory, nodes do not require extra disk space. This new behavior is enabled by default and does not require configuration.

Version changes

Prerequisites and notes

• You can upgrade to v6.2.12 from Redis Enterprise Software v6.0 and later.
• Refer to v6.2.4 release notes for important notes regarding changes made to the upgrade policy and how those changes might impact your experience.
• Upgrades from versions earlier than v6.0 are not supported.
• If you are using the earlier cluster-based LDAP mechanism, you must migrate to the role-based mechanism before upgrading to v6.2.12. For details, see Migrate to role-based LDAP.
• If you plan to upgrade your cluster to RHEL 8, see the v6.2.8 release notes for known limitations.

Future deprecation notice

TLS 1.0 and TLS 1.1

TLS 1.0 and TLS 1.1 connections are considered deprecated in favor of TLS 1.2 or later. Please verify that all clients, apps, and connections support TLS 1.2. Support for the earlier protocols will be removed in a future release. Certain operating systems, such as RHEL 8, have already removed support for the earlier protocols. Redis Enterprise Software cannot support connection protocols that are not supported by the underlying operating system.

Product lifecycle updates

Redis Enterprise Software v6.0.x will reach end of life (EOL) on May 31, 2022. To learn more, see the Redis Enterprise Software product lifecycle, which details the release number and the end-of-life schedule for Redis Enterprise Software. For Redis modules information and lifecycle, see Module lifecycle.

Redis modules

Redis Enterprise Software v6.2.12 includes the following Redis modules:

• RediSearch v2.4.9
• RedisJSON v2.0.11
• RedisBloom v2.2.17
• RedisGraph v2.8.15
• RedisTimeSeries v1.6.16

For help upgrading a module, see Add a module to a cluster.

Interface enhancements

• Allow creation and editing of sharded databases with a single shard. This lets you prepare for future scaling by ensuring your apps work in clustering mode, regardless of the actual number of configured shards
• Enhanced the slowlog in the UI to display unprintable characters in RESTORE commands
• Added support for custom paths when bootstrapping the cluster via the UI
• Improve readability of geo-distributed log entries in the UI

Additional enhancements

• Added support for the MODULE LIST command on Active-Active databases
• Enhanced validity checks of the input parameters of the CRDB-CLI tool

Resolved issues

• RS38320 A failed task leaves the nodes list outdated in the UI
• RS73768, RS72082 Increased certificate rotation timeout to allow it to finish
• RS72466, RS68668 Fix false positive alerts for certification expiration
• RS69256 Change pre-bootstrap default TLS version to 1.2
• RS67133 Fixed replication for command RESTOREMODAUX
• RS66468 Fixed "Test regex keys" in the UI
• RS58156 Fixed the installation to abort and alert when encountering issues in NTP
• RS67935 Fixed releasing 30MB of memory when deleting an Active-Active database
• RS64276 Fixed high memory consumption of the DMC output buffers when running CLIENT LIST

Known limitations

• RS81463 A shard may crash when resharding an Active-Active database with Auto Tiering . Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.
• RS54131 Returning +OK reply from the QUIT command on a TLS enabled database
• RS40641 - API requests are redirected to an internal IP in case the request arrives from a node which is not the master. To avoid this issue, use rladmin cluster config to configure handle_redirects or handle_metrics_redirects.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories. As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Security

Open Source Redis Security fixes compatibility

As part of Redis commitment to security, Redis Enterprise Software implements the latest security fixes available with open source Redis. The following Open Source Redis CVEs do not affect Redis Enterprise:

• CVE-2022-24834 - Redis Enterprise versions 6.2.12 and later are not impacted by the CVE that was found and fixed in open source Redis. A fix to prevent Lua scripts from causing heap overflow was implemented in Redis Enterprise version 6.2.12. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 7.0.12, Redis 6.2.13, Redis 6.0.20)
• CVE-2021-32625 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis since Redis Enterprise does not implement LCS. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.4, Redis 6.0.14)
• CVE-2021-32672 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the LUA debugger is unsupported in Redis Enterprise. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
• CVE-2021-32675 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the proxy in Redis Enterprise does not forward unauthenticated requests. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
• CVE-2021-32762 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the memory allocator used in Redis Enterprise is not vulnerable. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
• CVE-2021-41099 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the proto-max-bulk-len CONFIG is blocked in Redis Enterprise. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16) security fixes for recent CVEs.

Redis Enterprise has already included the fixes for the relevant CVEs. Some CVEs announced for open source Redis do not affect Redis Enterprise due to different and additional functionality available in Redis Enterprise that is not available in open source Redis.

Features and enhancements

Python 3 support. RHEL 8.5 support.

Redis Enterprise Software version 6.2.10 is now available!

The following table shows the MD5 checksums for the available packages.

• Upgrade the Redis Enterprise infrastructure to Python v3.9.
• Red Hat Enterprise Linux (RHEL) v8.5 and Red Hat Enterprise Linux (RHEL) v8.6 is now a supported platform.
• Oracle Linux v8 is now a supported platform.
• Compatibility with open source Redis 6.2.5.
• Compatibility with the security fixes of the latest open source Redis 6.2.6.
• Enhancements and bug fixes.

Version changes

Prerequisites and notes

• You can upgrade to v6.2.10 from Redis Enterprise Software v6.0 and later.
• Refer to v6.2.4 release notes for important notes regarding changes made to the upgrade.
• Upgrades from versions earlier than v6.0 are not supported.
• If you plan to upgrade your cluster to RHEL 8, refer to v6.2.8 release notes for known limitations.
• If you are using Active-Active or Active-Passive (ReplicaOf) databases and experience synchronization issues as a result of the upgrade, see RS67434 details in Resolved issues for help resolving the problem.

Product lifecycle updates

Redis Enterprise Software v6.0.x will reach end of life (EOF) on May 31, 2022.

To learn more, see the Redis Enterprise Software product lifecycle, which details the release number and the end-of-life schedule for Redis Enterprise Software.

For Redis modules information and lifecycle, see Module lifecycle.

Redis modules

Redis Enterprise Software v6.2.10 includes the following Redis modules:

• RediSearch v2.2.6
• RedisJSON v2.0.6
• RedisBloom v2.2.9
• RedisGraph v2.4.12
• RedisTimeSeries v1.4.13

Starting with Redis Enterprise Software v6.2.10 build 121, the included modules versions are:

• RediSearch v2.4.6
• RedisJSON v2.0.8
• RedisBloom v2.2.14
• RedisGraph v2.8.12
• RedisTimeSeries v1.6.9

For help upgrading a module, see Add a module to a cluster.

Interface enhancements

• When choosing RedisJSON, the user interface (UI) now suggests RedisSearch as well. To learn more, see the RedisJSON preview announcement, which details the benefits of combining RedisJSON and RediSearch.
• Adds the ability to sort the columns of the node list (RS48256).
• When creating a new geo-distributed (Active-Active) database, an endpoint port is no longer required. The system assigns one if none if provided (RS27632).

Additional enhancements

• Added an option to run a connectivity health check for the management layer of Active-Active databases. Run the following REST API command:
  GET https://[host][:port]/v1/crdbs/<crdb_guid>/health_report
• Added TLS handshake error messages to the DMC proxy log (RS59346).

Resolved issues

• RS58219 - Fixes a UI error message that showed a path instead of a relevant error message.
• RS44958 - Fixes incorrect description for the graph "incoming traffic" in Active-Active (geo-distributed) database UI Metrics.
• RS66280 - Fixes the lexicographic SORT command on Active-Active databases (e.g. SORT mylist ALPHA). The SORT command should only run on keys mapped to the same slot.
• RS64575 - Fixes a bug in the replication between primary and replica shards of a destination Active-active database in the scenario of using Replica-Of from a single to an Active-Active database, where the syncer process went down during the full sync.
• RS65370 - Adds logic to remove old syncer entries in the cluster configuration during upgrades.
• RS67434 - Version 6.2.10 fixes the mTLS handshake between the syncer process and the proxy (DMC), where the proxy presented a leaf certificate without its full chain to the syncer. After upgrading to 6.2.10, syncer connections using invalid certificates will break the synchronization between Active-Active instances or deployments using Replica Of when TLS is enabled. To ensure certificates are valid before upgrading do the following:
  • For Active-Active databases, run the following command from one of the clusters:
    crdb-cli crdb update --crdb-guid <CRDB-GUID> --force
  • For Active-Passive (Replica Of) databases: use the admin console to verify that the destination syncer has the correct certificate for the source proxy (DMC). For details, see Configure TLS for Replica Of.

Issues resolved in build 96

• RS67133 - An issue in Redis Enterprise Software affected replication in replica databases using RedisGraph, RediSearch, and RedisGears in specific scenarios. The problem appeared when importing an RDB file or while synchronizing target Active-Passive (ReplicaOf) databases.
  This issue is fixed in Redis Enterprise Software v6.2.10-96 and RedisGraph v2.8.11. We recommend upgrading to these versions at your earliest opportunity. (Failure to upgrade can lead to data loss.)
  Once the upgrades are complete, secondary shards might need to be restarted. You can use rlutil to restart secondary shards:
  rlutil redis_restart redis=<shard-id1>,<shard-id2>,...

Issues resolved in build 100

• RS74171 - A new command was added as part of Redis 6.2: XAUTOCLAIM. When used in an Active-Active configuration, this command may cause Redis shards to crash, potentially resulting in data loss. The issue is fixed in Redis Enterprise Software version 6.2.12. Additionally, we recommend enabling AOF persistence for all Active-Active configurations.

Issues resolved in build 121

• RS68668, RS72082 - Improvements for internode encryption certification rotation
• RS72304 - Avoid starting a master shard when both master and replica shards crash and the replica did not finish recovery
• RS74469 - Fix for some Redis Active-Active + Redis Streams scenarios that could lead to shard crash during backup; failure to backup

Issues resolved in build 129

• RS77003 - Add grace time to job scheduler to allow certificate rotation in case of failure due to scheduling conflicts.
• RS71112 - Update validation during db configuration to not fail due to ports associated with nodes that are no longer in the cluster. This was done to allow db configuration during adding and removing nodes as part of load balancing.
• RS78486 - Fix known issue from 6.2.10 build 100 - When using rladmin tune db to change the replica buffer size, the command appears to succeed, but the change does not take effect.

Known limitations

• RS81463 - A shard may crash when resharding an Active-Active database with Auto Tiering. Specifically, the shard will crash when volatile keys or Active-Active tombstone keys reside in Flash memory.
• RS78364 - When using rladmin tune db to change the replica buffer size, the command appears to succeed, but the change does not take effect. This issue was introduced in build 100; it will be fixed in a future build of Redis Enterprise Software v6.2.10 and in the next release (v6.2.12).
• RS63258 - Redis Enterprise Software is not currently supported on RHEL 8 with FIPS enabled.
  FIPS changes system-generated keys, which can limit secure access to the cluster or the admin console via port 8443.
• RS63375 - RHEL 7 clusters cannot be directly upgraded to RHEL 8 when hosting databases using modules.
  Due to binary differences in modules between the two operating systems, you cannot directly update RHEL 7 clusters to RHEL 8 when those clusters host databases using modules. Instead, you need to create a new cluster on RHEL 8 and then migrate existing data from your RHEL 7 cluster. This does not apply to clusters that do not use modules.

All known limitations listed in the v6.2.4 release notes have been addressed.

Installation limitations

Several Redis Enterprise Software installation reference files are installed to the directory /etc/opt/redislabs/ even if you use custom installation directories.

As a workaround to install Redis Enterprise Software without using any root directories, do the following before installing Redis Enterprise Software:

1. Create all custom, non-root directories you want to use with Redis Enterprise Software.
2. Mount /etc/opt/redislabs to one of the custom, non-root directories.

Known issues

• The ZRANGESTORE command, with a special zset-max-ziplist-entries configuration can crash Redis 6.2. See Redis repository 10767 for more details.
• RS40641 - API requests are redirected to an internal IP in case the request arrives from a node which is not the master. To avoid this issue, use rladmin cluster config to configure handle_redirects or handle_metrics_redirects.

Security

Open Source Redis Security fixes compatibility

As part of Redis commitment to security, Redis Enterprise Software implements the latest security fixes available with open source Redis. The following Open Source Redis CVE’s do not affect Redis Enterprise:

• CVE-2021-32625 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis since Redis Enterprise does not implement LCS. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.4, Redis 6.0.14)
• CVE-2021-32672 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the LUA debugger is unsupported in Redis Enterprise. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
• CVE-2021-32675 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the proxy in Redis Enterprise does not forward unauthenticated requests. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
• CVE-2021-32762 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the memory allocator used in Redis Enterprise is not vulnerable. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)
• CVE-2021-41099 - Redis Enterprise is not impacted by the CVE that was found and fixed in open source Redis because the proto-max-bulk-len CONFIG is blocked in Redis Enterprise. Additional information about the open source Redis fix is on the Redis GitHub page (Redis 6.2.6, Redis 6.0.16)security fixes for recent CVE’s. Redis Enterprise has already included the fixes for the relevant CVE’s. Some CVE’s announced for Open Source Redis do not affect Redis Enterprise due to different and additional functionality available in Redis Enterprise that is not available in Open Source Redis.