ContextQMD
Back to Redis

Rs 6 2 18 49

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

latest2.6 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-49 October release)
Ubuntu 1689029a28a2b0e3ad379559b94d00ae32
Ubuntu 18830e8704c0f6902a04df9ff53cc5e41f
RedHat Enterprise Linux (RHEL) 7
Oracle Enterprise Linux (OL) 7766d2f8448fc28d0ea67cac20387a9e3
RedHat Enterprise Linux (RHEL) 8
Oracle Enterprise Linux (OL) 87e31fb3e3416b404513dad508669f836

New features and enhancements

  • The [/nodes/status]({{< relref "/operate/rs/references/rest-api/requests/nodes/status" >}}) REST API endpoint indicates whether a node is the primary. (RS82566)
  • Added metrics to track certificates expiration time (RS56040)

Redis modules

Redis Enterprise Software v6.2.18-49 (October release) includes the following Redis modules:

  • [RediSearch v2.4.11]({{< relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.4-release-notes#v2411-july-2022" >}})
  • [RedisJSON v2.2.0]({{< relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.2-release-notes#v220-july-2022" >}})
  • [RedisBloom v2.2.18]({{< relref "/operate/oss_and_stack/stack-with-enterprise/bloom" >}}release-notes/redisbloom-2.2-release-notes/#v2218-july-2022)
  • [RedisGraph v2.8.17]({{< relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redisgraph/redisgraph-2.8-release-notes#v2817-july-2022" >}})
  • [RedisTimeSeries v1.6.17]({{< relref "operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.6-release-notes#v1617-july-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.

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.