Redis Enterprise Software release notes 8.0.x

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 Enterprise Software version 8.0 is now available!

Highlights

This version offers:

• Redis 8.0 and 8.2 feature set versions

• Performance improvements and memory reduction

• New vector set data structure

• Redis Flex revamped engine

• Redis Query Engine 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

Detailed release notes

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

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.

Breaking changes

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 the Redis Query Engine 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 Query Engine changes

The following changes affect behavior and validation in the Redis Query Engine:

• 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.

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.

Redis Query Engine 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 Enterprise Software and Redis Stack modules.

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

1. The RHEL-compatible distributions CentOS, CentOS Stream, Alma, and Rocky are supported if they have full RHEL compatibility. Oracle Linux running the Red Hat Compatible Kernel (RHCK) is supported, but the Unbreakable Enterprise Kernel (UEK) is not supported.

2. The server version of Ubuntu is recommended for production installations. The desktop version is only recommended for development deployments.

3. See the Redis Enterprise for Kubernetes documentation for details about support per version and Kubernetes distribution.

4. Docker images of Redis Enterprise Software are certified for development and testing only.

5. Supported only if FIPS was enabled during RHEL installation to ensure FIPS compliance.

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.

Known limitations

Rolling upgrade limitation for clusters with custom or deprecated modules

Due to module handling changes introduced in Redis Enterprise 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.