Redis Enterprise Software (RS) 5.4.6 is now available. This release includes the latest version of Redis 5 (5.0.5), bundles the GA release of the new RedisTimeSeries module, and adds other enhancements & bug fixes.

Overview

Follow these instructions for upgrading to RS 5.4.6 from RS 5.0 and above. If you have a version older than 5.0, you must first upgrade to version 5.2 (or at least 5.0).

New Features

Time Series

New GA release of the RedisTimeSeries (version v1.0.0) module is bundled in RS 5.4.6.

Modules Versions

Updated versions of GA modules:

Additional Capabilities

  • Latest version of Redis 5 (5.0.5) was merged into RS 5.4.6.
  • If a user subscribes to a channel during recovery of a Active-Active Redis (CRDB) from an Append Only File (AOF), the user receives only the new messages. (Fixes known limitation from RS 5.4.4)
  • CROSSSLOT behavior now matches Redis OSS behavior for accessing multiple keys in a single command. Now, when you use CRC16 hash function (default), you can pass a command for different keys/tags that are mapped to the same slot. (RS23189)
  • Cluster upgrade process was improved so that the duration of the cluster upgrade process reduced.

Information

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

Important Fixes

  • RS28679 - Syncer and peers related statistics for Active-Active Redis (CRDB), which are already available with the REST API, are exposed through Prometheus.
  • RS28946 - Metrics exporter related minor memory leak fix.
  • RS26312 - Ports handling during installation fix.
  • RS31703 - Fixed performance issue with MSET command.

Known Limitations

Upgrade

  • RS 5.4.2 introduced new Active-Active Redis (CRDB) capabilities that improve its compatibility with open source Redis. Now the string data-type in Active-Active Redis (CRDB) 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 CRDB protocol.
  • Before you upgrade a database with RediSearch Module to Redis 5.0, you must upgrade the RediSearch Module to version 1.4.2 or above.
  • 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.
  • We recommend that you test module upgrade commands in a test environment before you upgrade modules in a production environment. The module upgrade arguments are not validated during the upgrade process and incorrect arguments can cause unexpected downtime.
  • 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.

Cluster API

  • The API for removing a node is updated in RS 5.4.2 or higher. The API call must include json data and the "Content-Type: application/json" header. For example:

    curl -X POST -H "Content-Type: application/json" -i -k -u user@redislabs.com:passsword https://localhost:9443/v1/nodes/3/actions/remove --data "{}"

Redis Commands

  • The capability of disabling specific Redis commands does not work on commands specific to Redis Modules.
  • The CLIENT ID command cannot guarantee incremental IDs between clients that connect to different nodes under multi proxy policies.
  • CLIENT UNBLOCK command is not supported in RS 5.4 and above
  • Starting from RS 5.4.2 and after upgrading the CRDB, TYPE command for string data-type in CRDBs return "string" (OSS Redis standard).