ContextQMD
Back to Redis

Rs 6 2 18 58

content/operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58.md

latest2.3 KB
Original Source

This is a maintenance release for ​​Redis Enterprise Software version 6.2.18.

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

PackageMD5 checksum (6.2.18-58 November release)
Ubuntu 1638d974c47004df0808b71c2bd5a96996
Ubuntu 186a5ca7a287f1808a50d13312162aac4b
RedHat Enterprise Linux (RHEL) 7
Oracle Enterprise Linux (OL) 7d8283a3475a70823641249e3cfe3ab6e
RedHat Enterprise Linux (RHEL) 8
Oracle Enterprise Linux (OL) 8040e45c866fde391b35ae85d648a4afa

New features and enhancements

  • Added support to the UI to work with custom REST API port (RS84428)
  • Added info level print to redis_mgr for troubleshooting (RS85385)

Redis modules

Redis Enterprise Software v6.2.18-58 (November release) includes newer versions of the following Redis modules:

  • [RediSearch v2.4.14]({{< relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.4-release-notes#v2414-august-2022" >}})
  • [RedisGraph v2.8.19]({{< relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.8-release-notes#v2819-august-2022" >}})

See [Upgrade modules]({{< relref "/operate/oss_and_stack/stack-with-enterprise/install/upgrade-module" >}}) to learn how to upgrade a module for a database.

Resolved issues

  • RS85369 - Fixes umask validation during installation to allow for temporary umask change
  • RS77339 - Fixes the "FROM" email addresses of email alerts
  • RS86005 - Fixes bdbs/<int:uid>/actions/recover API to return the bdb status and not the recovery_plan

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

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

  2. From the admin console's redis modules tab, validate that these modules with their specific versions are loaded to the cluster.

  3. If one or more of the modules/versions are missing or if you need help, contact Redis support before taking additional steps.