Redis Enterprise Software release notes 7.22.x

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.

​​Redis Enterprise Software version 7.22 is now available!

Highlights

This version offers:

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

Version changes

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

Deprecations

API deprecations

• Deprecated GET /v1/bdbs/<uid>/actions/optimize_shards_placement REST API request. Use PUT /v1/bdbs/<uid>/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.

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 Enterprise 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. As a workaround, use this query to measure availability:

  endpoint_server_became_unavailable{cluster="$cluster", db="$db"} 
  - 
  endpoint_server_available_again{cluster="$cluster", db="$db"}
  

  For up: 0-2

  For down: 2-1000000

• RS156570: Redis Enterprise Software version 7.22.0 can experience a significant performance impact when using search indexes with vector fields of type HNSW. This issue is characterized by elevated CPU usage, even during idle periods, due to periodic database information collection for metrics and monitoring. This behavior can also affect other database operations. For example, the FT.INFO command can become long-running on such indexes.

• RS156391: The job_scheduler's memory usage can increase significantly when the diagnostic logging service is enabled.

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