diff --git a/content/operate/rs/databases/active-active/manage.md b/content/operate/rs/databases/active-active/manage.md index 0785cacd05..02b7819328 100644 --- a/content/operate/rs/databases/active-active/manage.md +++ b/content/operate/rs/databases/active-active/manage.md @@ -12,13 +12,98 @@ weight: 30 You can configure and manage your Active-Active database from either the Cluster Manager UI or the command line. -To change the global configuration of the Active-Active database, use [`crdb-cli`]({{< relref "/operate/rs/references/cli-utilities/crdb-cli" >}}). - -If you need to apply changes locally to one database instance, you use the Cluster Manager UI or [`rladmin`]({{< relref "/operate/rs/references/cli-utilities/rladmin" >}}). ## Database settings -Many Active-Active database settings can be changed after database creation. One notable exception is database clustering. Database clustering can't be turned on or off after the database has been created. +Most Active-Active database settings can be changed after database creation. One notable exception is database clustering, which can't be turned on or off after the database has been created. + +As of Redis Software version 8.0.16, the Cluster Manager UI supports both [global](#change-global-configuration) and [local](#change-local-configuration) configuration changes for Active-Active databases. In earlier versions, configuration changes made in the Cluster Manager UI applied only to the local instance and required additional manual updates for each participating cluster. + +### Change global configuration + +Global configuration changes are applied to all participating clusters in the Active-Active database. However, if your Active-Active mesh contains local configurations, they will continue to override global settings on the database instances where they are applied. + +{{< warning >}} +Applying global configuration changes will override any local settings created using the API or earlier Cluster Manager UI versions. To keep local changes, manage them in the [**Local** configuration tab](#change-local-configuration). +{{< /warning >}} + +
+ +{{< multitabs id="change-global-config-methods" +tab1="Cluster Manager UI" +tab2="crdb-cli" >}} + +To make global configuration changes in the Cluster Manager UI: + +1. Select the Active-Active database from the **Databases** list and go to its **Configuration** screen. + +1. While on the **Global** tab, click **Edit**. + + The global configuration tab is selected. + +1. Make your configuration changes. + +1. Click **Save** to apply the changes globally to all participating clusters. + +-tab-sep- + +To change the global configuration from the command line, use [`crdb-cli crdb update`]({{< relref "/operate/rs/references/cli-utilities/crdb-cli/crdb/update" >}}): + +```sh +crdb-cli crdb update --crdb-guid -- +``` + +Replace the placeholders `` with your own values. + +{{< /multitabs >}} + +### Change local configuration + +Local configuration changes override global configuration settings and are applied only to the database instance on the current cluster. + +To apply changes to a local Active-Active database instance, use one of the following methods: + +{{< multitabs id="change-local-config-methods" +tab1="Cluster Manager UI" +tab2="rladmin" >}} + +To change the local configuration in the Cluster Manager UI: + +1. Select the Active-Active database from the **Databases** list and go to its **Configuration** screen. + +1. Go to the **Local** tab. + + The local configuration tab is selected. + +1. Click **Edit**, then make your configuration changes. + +1. Click **Save** to apply the changes to the current database instance only. + +-tab-sep- + +To change the local configuration from the command line, use [`rladmin tune db`]({{< relref "/operate/rs/references/cli-utilities/rladmin/tune#tune-db" >}}): + +```sh +rladmin tune db { db: | } +``` + +Replace the placeholders `` with your own values. + +{{< /multitabs >}} + +### View differences between global and local configuration + +In the Cluster Manager UI, an Active-Active database's **Global** configuration tab indicates when a local configuration differs from the global configuration: + +{{On the global configuration tab, a warning is visible that says: 'This Active Active mesh contains local configurations which will not be affected by the global settings'.}} + +If a warning symbol appears next to a setting on the **Global** configuration tab, point to the warning symbol to show details about the local configuration differences: + +{{An example that shows memory eviction is set to noeviction globally but allkeys-lru locally.}} + +On the **Local** configuration tab, any locally configured settings that differ from the global settings are marked with a **Local configuration** label: + +{{A local configuration label appears next to Memory eviction allkeys-lru.}} ## Participating clusters diff --git a/content/operate/rs/monitoring/health-report.md b/content/operate/rs/monitoring/health-report.md new file mode 100644 index 0000000000..36ff10997b --- /dev/null +++ b/content/operate/rs/monitoring/health-report.md @@ -0,0 +1,142 @@ +--- +Title: Consolidated health report +alwaysopen: false +categories: +- docs +- operate +- rs +description: View the consolidated health report to get a read-only snapshot of a Redis Software cluster's current system health. +linkTitle: Consolidated health report +weight: 78 +tocEmbedHeaders: true +--- + +The consolidated health report is a read-only, consolidated snapshot of a cluster's current system health, including: + +- License and certificate status + +- Nodes and services health + +- Node memory breakdown, including free and provisioned memory + +- Running actions status + +- Active alerts + +- Basic database status and version + +- High availability health + +The consolidated health report consolidates cluster and database health information that was previously scattered across multiple APIs and CLI commands, such as [`rladmin status extra all`]({{}}) and required SSH access to view. + +As of Redis Software version 8.0.16, you can access the cluster and database health reports using the [Cluster manager UI](#view-health-overview) or [REST API requests](#health-rest-api-requests). + +## View health overview {#view-health-overview} + +You can access the cluster and database health reports using the **Overview** screen in the Cluster Manager UI. + +You can view node health + +{{The health report screen.}} + +### Cluster info + +The **Cluster Info** section provides basic cluster details, including: + +- Overall cluster status + +- Redis Software cluster version + +- License usage and expiration date + +### Cluster storage + +The **Cluster Storage** section provides memory usage details, including used memory, free memory, and total memory for RAM, flash, persistent storage, and ephemeral storage on the cluster. + +### Nodes + +The **Nodes** section shows the status of nodes in the cluster and indicates which node is the leader or primary node. + +### Databases + +In the **Databases** section, you can check each database's status and Redis version. You can click the number listed by each field to display the relevant database names and click on the database links to view database details. + +{{Active database names and links are displayed.}} + +### Certificates + +The **Certificates** section shows whether the cluster's certificates are still valid. If a certificate appears as no longer valid, you can click the **Certificates** link to update the certificate. + +{{The certificates section shows an alert that the SSO service certificate expires soon.}} + +### Actions + +In the **Actions** section, you can view currently running actions. + +{{The Actions section shows a database upgrade is in progress.}} + +### Alerts and services + +If a configured alert threshold is reached or a running service stops, an alert will appear in the **Alerts & Services** section. + +{{Active alerts are displayed ephemeral and persistent storage have reached 90% capacity.}} + +## View node health {#view-node-health} + +On the **Nodes** screen of the Cluster Manager UI, you can click on a node to go to its **Node configuration** tab and view node health details. + +{{Node configuration screen.}} + +### Verify nodes + +You can check if nodes are functioning properly using one of the following methods: + +{{< multitabs id="verify-nodes" + tab1="Verify all nodes" + tab2="Verify specific node" >}} + +On the **Nodes** screen, click **Verify all nodes**. + +-tab-sep- + +1. On the **Nodes** screen, find the node you want verify in the list and click the **More actions** button (**⋮**). + +1. Select **Verify node** from the list. + +Click the more actions button for a node to access node actions. + +{{< /multitabs >}} + +### Node storage + +The **Node storage** section of the **Node configuration** tab provides memory usage details, including used memory, free memory, and total memory for RAM, flash, persistent storage, and ephemeral storage on the node. + +### Services + +In the **Services** section **Node configuration** tab, you can view the list of services running on the node and the most recent status of each. + +{{The services section shows most services running and one stopped service.}} + +### Shards + +When viewing a node's configuration, you can click the **Shards** tab to view a list of database shards running on the node and related details such as each shard's ID, current status, role, and slot range. + +{{A list of database shards on the node.}} + +## Health report REST API requests {#health-rest-api-requests} + +### Cluster health report requests + +[Cluster health report]({{}}) REST API requests provide overall health information for a cluster: + +```sh +GET https://:/v4/cluster/health +``` + +### Database health report requests + +[Database health report]({{}}) REST API requests provide detailed health information for a specific database: + +```sh +GET https://:/v4/bdb//health +``` diff --git a/content/operate/rs/references/rest-api/objects/cluster/_index.md b/content/operate/rs/references/rest-api/objects/cluster/_index.md index 64e2e96098..aa45c5700a 100644 --- a/content/operate/rs/references/rest-api/objects/cluster/_index.md +++ b/content/operate/rs/references/rest-api/objects/cluster/_index.md @@ -83,6 +83,7 @@ An API object that represents the cluster. | smtp_tls_mode | "none"
"starttls"
"tls" | Specifies which TLS mode to use for SMTP access | | smtp_use_tls | boolean (default: false) | Use TLS for SMTP access (deprecated as of Redis Software v4.3.3, use smtp_tls_mode field instead) | | smtp_username | string | SMTP server username (pattern does not allow special characters &,\<,>,") | +| state_machine_smart_client_handoffs_delay_ms | integer (range: 0-10000) (default: 2000) | For smart client handoffs feature, the time in milliseconds to pause the state machine between sending the notification to clients and performing the operation | | syncer_certificate | string | Cluster's syncer certificate | | upgrade_mode | boolean (default: false) | Is cluster currently in upgrade mode | | use_external_ipv6 | boolean (default: true) | Should redislabs services listen on ipv6 | diff --git a/content/operate/rs/release-notes/rs-8-0-releases/_index.md b/content/operate/rs/release-notes/rs-8-0-releases/_index.md index b7c677b2c2..ae96f5e9f6 100644 --- a/content/operate/rs/release-notes/rs-8-0-releases/_index.md +++ b/content/operate/rs/release-notes/rs-8-0-releases/_index.md @@ -55,7 +55,7 @@ For more detailed release notes, select a build version from the following table ### Breaking changes -- LDAP filters for `user_dn_query` and `dn_group_query` now strictly require parentheses to function correctly. Filters that previously worked without parentheses will no longer work after upgrading to Redis Software 8.0.x. For example, you must include the parentheses in `(sAMAccountName=%u)`. +- For Redis Software versions 8.0.2 through 8.0.10, LDAP filters for `user_dn_query` and `dn_group_query` strictly require parentheses to function correctly. Filters that previously worked without parentheses will no longer work after upgrading to these versions. For example, you must include the parentheses in `(sAMAccountName=%u)`. As of version 8.0.16, this breaking change no longer applies, and both `(sAMAccountName=%u)` and `sAMAccountName=%u` are valid filters. - Redis Software installation script changes: @@ -145,6 +145,8 @@ See [Ports and port ranges used by Redis Software]({{}}) REST API requests. Use the new module configuration objects `search`, `timeseries`, and `probabilistic` instead. +- Deprecated `event_archive_cleanup_task_settings` for `job_scheduler` REST API requests. + #### Redis Search deprecations - Deprecated commands: `FT.ADD`, `FT.SAFEADD`, `FT.DEL`, `FT.GET`, `FT.MGET`, `FT.SYNADD`, `FT.DROP`, `FT._DROPIFX`, and `FT.CONFIG`. diff --git a/content/operate/rs/release-notes/rs-8-0-releases/rs-8-0-16-tba.md b/content/operate/rs/release-notes/rs-8-0-releases/rs-8-0-16-tba.md new file mode 100644 index 0000000000..59370ff766 --- /dev/null +++ b/content/operate/rs/release-notes/rs-8-0-releases/rs-8-0-16-tba.md @@ -0,0 +1,469 @@ +--- +Title: Redis Software release notes 8.0.16-tba (March 2026) +alwaysopen: false +categories: +- docs +- operate +- rs +compatibleOSSVersion: Redis 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, 6.2.13 +description: Consolidated health report. Global Active-Active configuration in the Cluster Manager UI. +linkTitle: 8.0.16-tba (March 2026) +weight: 85 +--- + +​[​Redis Software version 8.0.16](https://redis.io/downloads/#Redis_Software) is now available! This release includes API enhancements that warranted a new minor version instead of a maintenance release for version 8.0.10. However, you can upgrade from 8.0.2, 8.0.6, or 8.0.10 to 8.0.16 without issue. + +## Highlights + +This version offers: + +- Consolidated health report + +- Global Active-Active configuration in the Cluster Manager UI + +## New in this release + +### New features + +#### Consolidated health report + +Redis Software's new health report is a read-only, consolidated snapshot of a cluster's current system health, including: + + - License and certificate status + + - Nodes and services health + + - Node memory breakdown, including free and provisioned memory + + - Running actions status + + - Active alerts + + - Basic database status and version + + - High availability health + +The new health report consolidates cluster and database health information that was previously scattered across multiple APIs and CLI commands, such as [`rladmin status extra all`]({{}}) and required SSH access to view. + +Now, you can access the cluster and database health reports using the **Overview** screen in the Cluster manager UI or the new health API paths: + +- [Cluster health report]({{}}): + + ```sh + GET /v4/cluster/health + ``` + +- [Database health report]({{}}): + + ```sh + GET /v4/bdb//health + ``` + +For more information, see [Consolidated health report]({{}}). + +#### Global Active-Active configuration in the Cluster Manager UI + +The Cluster Manager UI now supports global configuration updates for Active-Active databases, bringing UI behavior in line with the CRDB API. + +Previously, when modifying Active-Active databases using the CRDB API, configuration changes were applied globally by default. However, when performing the same actions in the Cluster Manager UI, modifications applied only to the local instance, requiring additional manual updates for each instance in participating clusters. + +Global configuration is now the default in the Cluster Manager UI. You can still make local configuration changes when needed, which will override global settings on the database instances where they are applied. + +{{< warning >}} +Applying global configuration changes will override any local settings created using the API or earlier Cluster Manager UI versions. To preserve existing local changes, manage them in the **Local** configuration tab before applying global changes. +{{< /warning >}} + +For more information, see [Manage Active-Active databases]({{< relref "/operate/rs/databases/active-active/manage#database-settings" >}}). + +### Enhancements + +- Added the ability to undo configuration overrides for an Active-Active database instance and reset it to the default database configuration using a REST API request to [update an Active-Active database]({{}}). For example: + + ```sh + PATCH /v1/crdbs/ + { "instances": [{ + "db_uid": "", + "id": , + "db_config": { "": null } + } + ]} + ``` + +- For [smart client handoffs]({{}}), the delay between notifying clients and performing an operation is now configurable using the new `state_machine_smart_client_handoffs_delay_ms` cluster setting in the REST API. + +### Redis database versions + +Redis Software version 8.0.16 includes the following Redis database versions: 8.4.0, 8.2.1, 8.0.2, 7.4.3, 7.2.7, and 6.2.13. + +The [default Redis database version]({{}}) is 8.4. + +### Redis feature sets + +Redis Software includes multiple feature sets, compatible with different Redis database versions. + +The following table shows which Redis modules are compatible with each Redis database version included in this release. + +| Redis database version | Compatible Redis modules | +|------------------------|--------------------------| +| 8.4 | RediSearch 8.4
RedisJSON 8.4
RedisTimeSeries 8.4
RedisBloom 8.4
See [What's new in Redis 8.4]({{}}) and [Redis Open Source 8.4 release notes]({{}}) | +| 8.2 | RediSearch 8.2
RedisJSON 8.2
RedisTimeSeries 8.2
RedisBloom 8.2
See [What's new in Redis 8.2]({{}}) and [Redis Open Source 8.2 release notes]({{}}) | +| 8.0 | RediSearch 8.0
RedisJSON 8.0
RedisTimeSeries 8.0
RedisBloom 8.0
See [What's new in Redis 8.0]({{}}) and [Redis Open Source 8.0 release notes]({{}}) | +| 7.4 | [RediSearch 2.10]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.10-release-notes.md" >}})
[RedisJSON 2.8]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md" >}})
[RedisTimeSeries 1.12]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.12-release-notes.md" >}})
[RedisBloom 2.8]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md" >}}) | +| 7.2 | [RediSearch 2.8]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.8-release-notes.md" >}})
[RedisJSON 2.6]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md" >}})
[RedisTimeSeries 1.10]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.10-release-notes.md" >}})
[RedisBloom 2.6]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.6-release-notes.md" >}}) | +| 6.2 | [RediSearch 2.6]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisearch/redisearch-2.6-release-notes.md" >}})
[RedisJSON 2.4]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md" >}})
[RedisTimeSeries 1.8]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redistimeseries/redistimeseries-1.8-release-notes.md" >}})
[RedisBloom 2.4]({{< relref "/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.4-release-notes.md" >}}) | + +### Resolved issues + +- RS168233: Fixed an issue where Active-Active database instance removal could fail with authentication errors if the default database password was enabled during database creation and deactivated after creation. + +- RS150707: Fixed an issue where endpoint binding operations could become stuck if a node restarted during the binding process. + +- RS176558: Fixed a misleading error message that mentioned LDAP service problems when authentication issues occurred with Entra ID. + +- RS160689: Fixed an issue where `redis-cli INFO` could temporarily show an outdated data eviction policy after changing the policy in the Cluster Manager UI. + +- RS171340: Fixed an issue where `install.sh` would continue running even when required ports were already occupied. + +- RS171806: Fixed an issue where the `rladmin cluster running_actions` command could fail when active tasks did not have progress information available. + +- RS184175: Fixed an issue where active cluster alerts were not properly displayed in health reports. + +- RS128780: Reduced excessive logging by removing unnecessary "Dropping obsolete sample" message from the CCS log file. + +- RS185428: Improved error messages for missing root or chain of trust issues during certificate upload. + +- RS180061: Fixed an issue where user password update REST API requests would fail if the new password matched the current password. + +- RS176555: Fixed an issue that could cause the DMC to crash if a client disconnected during the authentication process. + +- RS167847: Fixed an issue where turning off `alert_mgr` also turned off `event_log`. + +- RS182007: Modified the custom installer script to prevent the creation of circular symlinks during cluster upgrades. + +- RS188362: Fixed an issue with missing metrics in the Cluster Manager UI. + +- RS189517: Fixed a breaking change where LDAP filters for `user_dn_query` and `dn_group_query` strictly required parentheses to function correctly. This change caused filters that previously worked without parentheses to stop working after upgrading to Redis Software version 8.0.x. As of version 8.0.16, this breaking change no longer applies, and both `(sAMAccountName=%u)` and `sAMAccountName=%u` are valid filters. + +## Version changes + +### Deprecations + +#### API deprecations + +- Deprecated `event_archive_cleanup_task_settings` for `job_scheduler` REST API requests. + +### Supported platforms + +The following table provides a snapshot of supported platforms as of this Redis Software release. See the [supported platforms reference]({{< relref "/operate/rs/references/supported-platforms" >}}) for more details about operating system compatibility. + +✅ Supported – The platform is supported for this version of Redis Software and Redis Stack modules. + +:warning: Deprecation warning – The platform is still supported for this version of Redis Software, but support will be removed in a future release. + +| Redis Software
major versions | 8.0 | 7.22 | 7.8 | 7.4 | 7.2 | 6.4 | 6.2 | +|---------------------------------|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:|:-----:| +| **Release date** | Oct 2025 | May 2025 | Nov 2024 | Feb 2024 | Aug 2023 | Feb 2023 | Aug 2021 | +| [**End-of-life date**]({{< relref "/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule" >}}) | Determined after
next major release | Oct 2027 | May 2027 | Nov 2026 | Feb 2026 | Aug 2025 | Feb 2025 | +| **Platforms** | | | | | | | | +| RHEL 9 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | – | – | – | +| RHEL 9
FIPS mode[5](#table-note-5) | ✅ | ✅ | ✅ | – | – | – | – | +| RHEL 8 &
compatible distros[1](#table-note-1) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| RHEL 7 &
compatible distros[1](#table-note-1) | – | – | – | – | :warning: | :warning: | :warning: | +| Ubuntu 22.04[2](#table-note-2) | ✅ | ✅ | ✅ | – | – | – | – | +| Ubuntu 20.04[2](#table-note-2) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – | +| Ubuntu 18.04[2](#table-note-2) | – | – | – | :warning: | :warning: | :warning: | :warning: | +| Ubuntu 16.04[2](#table-note-2) | – | – | – | – | :warning: | :warning: | :warning: | +| Amazon Linux 2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | – | +| Amazon Linux 1 | – | – | – | – | :warning: | :warning: | :warning: | +| Kubernetes[3](#table-note-3) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| Docker[4](#table-note-4) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | + +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]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for details about support per version and Kubernetes distribution. + +4. [Docker images]({{< relref "/operate/rs/installing-upgrading/quickstarts/docker-quickstart" >}}) of Redis Software are certified for development and testing only. + +5. Supported only if [FIPS was enabled during RHEL installation](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/security_hardening/switching-rhel-to-fips-mode_security-hardening#proc_installing-the-system-with-fips-mode-enabled_switching-rhel-to-fips-mode) to ensure FIPS compliance. + +## Downloads + +The following table shows the SHA256 checksums for the available packages: + +| Package | SHA256 checksum (8.0.16-tba March release) | +|---------|---------------------------------------| +| Ubuntu 20 | | +| Ubuntu 22 (amd64) | | +| Ubuntu 22 (arm64) | | +| Red Hat Enterprise Linux (RHEL) 8 | | +| Red Hat Enterprise Linux (RHEL) 9 (amd64) | | +| Red Hat Enterprise Linux (RHEL) 9 (arm64) | | +| Amazon Linux 2 | | + +## Known issues + +- RS155734: Endpoint availability metrics do not work as expected due to a calculation error. + +## Known limitations + +#### Trim ACKED not supported for Active-Active 8.4 databases + +For Active-Active databases running Redis database version 8.4, the `ACKED` option is not supported for trimming commands. + +#### Rolling upgrade limitation for clusters with custom or deprecated modules + +Due to module handling changes introduced in Redis 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. + +#### 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`]({{< relref "/operate/rs/references/cli-utilities/crdb-cli/crdb/purge-instance" >}}) instead. + +- Search and export the log. + +## Security + +#### Redis Open Source security fixes compatibility + +As part of Redis's commitment to security, Redis Software implements the latest [security fixes](https://github.com/redis/redis/releases) available with [Redis Open Source](https://github.com/redis/redis). Redis Software has already included the fixes for the relevant CVEs. + +Some CVEs announced for Redis Open Source do not affect Redis Software due to different or additional functionality available in Redis Software that is not available in Redis Open Source. + +Redis Software 8.0.16-tba supports Redis Open Source 8.4, 8.2, 8.0, 7.4, 7.2, and 6.2. Below is the list of Redis Open Source CVEs and other security vulnerabilities fixed by version. + +Redis 8.2.x: + +- RedisBloom: Restore invalid filter. + +- (CVE-2025-62507) A user can run the `XACKDEL` command with multiple IDs and trigger a stack buffer overflow, which can potentially lead to remote code execution. + +- The `HGETEX` command can lead to a buffer overflow. + +- Integer overflow in `hllPatLen`. + +- RedisBloom: Cuckoo filter counter overflow. + +- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes. + +- RedisBloom: Reachable assert in `TopK_Create` + +- RedisBloom: Out-of-bounds access with empty Bloom chains. + +- RedisBloom: Division by zero in Cuckoo filter insertion. + +- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user. + +- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service. + +- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution. + +- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution. + +Redis 8.0.x: + +- RedisBloom: Restore invalid filter. + +- The `HGETEX` command can lead to a buffer overflow. + +- Integer overflow in `hllPatLen`. + +- RedisBloom: Cuckoo filter counter overflow. + +- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes. + +- RedisBloom: Reachable assert in `TopK_Create` + +- RedisBloom: Out-of-bounds access with empty Bloom chains. + +- RedisBloom: Division by zero in Cuckoo filter insertion. + +- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user. + +- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service. + +- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution. + +- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution. + +Redis 7.4.x: + +- RedisBloom: Restore invalid filter. + +- Integer overflow in `hllPatLen`. + +- RedisBloom: Cuckoo filter counter overflow. + +- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes. + +- RedisBloom: Reachable assert in `TopK_Create` + +- RedisBloom: Out-of-bounds access with empty Bloom chains. + +- RedisBloom: Division by zero in Cuckoo filter insertion. + +- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user. + +- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service. + +- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution. + +- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution. + +- (CVE-2025-32023) An authenticated user can use a specially crafted string to trigger a stack/heap out-of-bounds write on HyperLogLog operations, which can lead to remote code execution. + +- (CVE-2025-21605) An unauthenticated client can cause unlimited growth of output buffers until the server runs out of memory or is terminated, which can lead to denial-of-service. + +Redis 7.2.x: + +- RedisBloom: Restore invalid filter. + +- Integer overflow in `hllPatLen`. + +- RedisBloom: Cuckoo filter counter overflow. + +- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes. + +- RedisBloom: Reachable assert in `TopK_Create` + +- RedisBloom: Out-of-bounds access with empty Bloom chains. + +- RedisBloom: Division by zero in Cuckoo filter insertion. + +- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user. + +- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service. + +- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution. + +- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution. + +- (CVE-2025-32023) An authenticated user can use a specially crafted string to trigger a stack/heap out-of-bounds write on HyperLogLog operations, which can lead to remote code execution. + +- (CVE-2025-21605) An unauthenticated client can cause unlimited growth of output buffers until the server runs out of memory or is terminated, which can lead to denial-of-service. + +- (CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution. + +- (CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as `KEYS`, `SCAN`, `PSUBSCRIBE`, `FUNCTION LIST`, `COMMAND LIST`, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes. + +- (CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers, which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution. + +- (CVE-2023-41053) Redis does not correctly identify keys accessed by `SORT_RO` and, as a result, may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. (Redis 7.2.1) + +Redis 7.0.x: + +- (CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution. + +- (CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as `KEYS`, `SCAN`, `PSUBSCRIBE`, `FUNCTION LIST`, `COMMAND LIST`, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes. + +- (CVE-2023-41056) In some cases, Redis may incorrectly handle resizing of memory buffers, which can result in incorrect accounting of buffer sizes and lead to heap overflow and potential remote code execution. + +- (CVE-2023-41053) Redis does not correctly identify keys accessed by `SORT_RO` and, as a result, may grant users executing this command access to keys that are not explicitly authorized by the ACL configuration. (Redis 7.0.13) + +- (CVE-2023-36824) Extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption, and potentially remote code execution. Specifically: using `COMMAND GETKEYS*` and validation of key names in ACL rules. (Redis 7.0.12) + +- (CVE-2023-28856) Authenticated users can use the `HINCRBYFLOAT` command to create an invalid hash field that will crash Redis on access. (Redis 7.0.11) + +- (CVE-2023-28425) Specially crafted `MSETNX` commands can lead to assertion and denial-of-service. (Redis 7.0.10) + +- (CVE-2023-25155) Specially crafted `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 7.0.9) + +- (CVE-2023-22458) Integer overflow in the Redis `HRANDFIELD` and `ZRANDMEMBER` commands can lead to denial-of-service. (Redis 7.0.8) + +- (CVE-2022-36021) String matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis can cause it to hang and consume 100% CPU time. (Redis 7.0.9) + +- (CVE-2022-35977) Integer overflow in the Redis `SETRANGE` and `SORT`/`SORT_RO` commands can drive Redis to OOM panic. (Redis 7.0.8) + +- (CVE-2022-35951) Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument, may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. The problem affects Redis versions 7.0.0 or newer. (Redis 7.0.5) + +- (CVE-2022-31144) A specially crafted `XAUTOCLAIM` command on a stream key in a specific state may result in heap overflow and potentially remote code execution. The problem affects Redis versions 7.0.0 or newer. (Redis 7.0.4) + +- (CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 7.0.12) + +- (CVE-2022-24736) An attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result in a crash of the `redis-server` process. This issue affects all versions of Redis. (Redis 7.0.0) + +- (CVE-2022-24735) By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. (Redis 7.0.0) + +Redis 6.2.x: + +- RedisBloom: Restore invalid filter. + +- Integer overflow in `hllPatLen`. + +- RedisBloom: Cuckoo filter counter overflow. + +- RedisBloom: Invalid Bloom filters can cause arbitrary memory reads and writes. + +- RedisBloom: Reachable assert in `TopK_Create` + +- RedisBloom: Out-of-bounds access with empty Bloom chains. + +- RedisBloom: Division by zero in Cuckoo filter insertion. + +- (CVE-2025-46818) An authenticated user may use a specially crafted Lua script to manipulate different LUA objects and potentially run their own code in the context of another user. + +- (CVE-2025-46819) An authenticated user may use a specially crafted LUA script to read out-of-bound data or crash the server and lead to subsequent denial of service. + +- (CVE-2025-46817) An authenticated user may use a specially crafted Lua script to cause an integer overflow and potentially lead to remote code execution. + +- (CVE-2025-49844) An authenticated user may use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free, and potentially lead to remote code execution. + +- (CVE-2025-32023) An authenticated user can use a specially crafted string to trigger a stack/heap out-of-bounds write on HyperLogLog operations, which can lead to remote code execution. + +- (CVE-2025-21605) An unauthenticated client can cause unlimited growth of output buffers until the server runs out of memory or is terminated, which can lead to denial-of-service. + +- (CVE-2024-31449) An authenticated user may use a specially crafted Lua script to trigger a stack buffer overflow in the bit library, which may potentially lead to remote code execution. + +- (CVE-2024-31228) An authenticated user can trigger a denial-of-service by using specially crafted, long string match patterns on supported commands such as `KEYS`, `SCAN`, `PSUBSCRIBE`, `FUNCTION LIST`, `COMMAND LIST`, and ACL definitions. Matching of extremely long patterns may result in unbounded recursion, leading to stack overflow and process crashes. + +- (CVE-2023-28856) Authenticated users can use the `HINCRBYFLOAT` command to create an invalid hash field that will crash Redis on access. (Redis 6.2.12) + +- (CVE-2023-25155) Specially crafted `SRANDMEMBER`, `ZRANDMEMBER`, and `HRANDFIELD` commands can trigger an integer overflow, resulting in a runtime assertion and termination of the Redis server process. (Redis 6.2.11) + +- (CVE-2023-22458) Integer overflow in the Redis `HRANDFIELD` and `ZRANDMEMBER` commands can lead to denial-of-service. (Redis 6.2.9) + +- (CVE-2022-36021) String matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis can cause it to hang and consume 100% CPU time. (Redis 6.2.11) + +- (CVE-2022-35977) Integer overflow in the Redis `SETRANGE` and `SORT`/`SORT_RO` commands can drive Redis to OOM panic. (Redis 6.2.9) + +- (CVE-2022-24834) A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson and cmsgpack libraries, and result in heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. (Redis 6.2.13) + +- (CVE-2022-24736) An attacker attempting to load a specially crafted Lua script can cause NULL pointer dereference which will result in a crash of the `redis-server` process. This issue affects all versions of Redis. (Redis 6.2.7) + +- (CVE-2022-24735) By exploiting weaknesses in the Lua script execution environment, an attacker with access to Redis can inject Lua code that will execute with the (potentially higher) privileges of another Redis user. (Redis 6.2.7) + +- (CVE-2021-41099) Integer to heap buffer overflow handling certain string commands and network payloads, when `proto-max-bulk-len` is manually configured to a non-default, very large value. (Redis 6.2.6) + +- (CVE-2021-32762) Integer to heap buffer overflow issue in `redis-cli` and `redis-sentinel` parsing large multi-bulk replies on some older and less common platforms. (Redis 6.2.6) + +- (CVE-2021-32761) An integer overflow bug in Redis version 2.2 or newer can be exploited using the `BITFIELD` command to corrupt the heap and potentially result with remote code execution. (Redis 6.2.5) + +- (CVE-2021-32687) Integer to heap buffer overflow with intsets, when `set-max-intset-entries` is manually configured to a non-default, very large value. (Redis 6.2.6) + +- (CVE-2021-32675) Denial Of Service when processing RESP request payloads with a large number of elements on many connections. (Redis 6.2.6) + +- (CVE-2021-32672) Random heap reading issue with Lua Debugger. (Redis 6.2.6) + +- (CVE-2021-32628) Integer to heap buffer overflow handling ziplist-encoded data types, when configuring a large, non-default value for `hash-max-ziplist-entries`, `hash-max-ziplist-value`, `zset-max-ziplist-entries` or `zset-max-ziplist-value`. (Redis 6.2.6) + +- (CVE-2021-32627) Integer to heap buffer overflow issue with streams, when configuring a non-default, large value for `proto-max-bulk-len` and `client-query-buffer-limit`. (Redis 6.2.6) + +- (CVE-2021-32626) Specially crafted Lua scripts may result with Heap buffer overflow. (Redis 6.2.6) + +- (CVE-2021-32625) An integer overflow bug in Redis version 6.0 or newer can be exploited using the STRALGO LCS command to corrupt the heap and potentially result with remote code execution. This is a result of an incomplete fix by CVE-2021-29477. (Redis 6.2.4) + +- (CVE-2021-29478) An integer overflow bug in Redis 6.2 could be exploited to corrupt the heap and potentially result with remote code execution. The vulnerability involves changing the default set-max-intset-entries configuration value, creating a large set key that consists of integer values and using the COPY command to duplicate it. The integer overflow bug exists in all versions of Redis starting with 2.6, where it could result with a corrupted RDB or DUMP payload, but not exploited through COPY (which did not exist before 6.2). (Redis 6.2.3) + +- (CVE-2021-29477) An integer overflow bug in Redis version 6.0 or newer could be exploited using the STRALGO LCS command to corrupt the heap and potentially result in remote code execution. The integer overflow bug exists in all versions of Redis starting with 6.0. (Redis 6.2.3) diff --git a/static/images/rs/screenshots/databases/active-active-databases/global-config-tab.png b/static/images/rs/screenshots/databases/active-active-databases/global-config-tab.png new file mode 100644 index 0000000000..853fbc770f Binary files /dev/null and b/static/images/rs/screenshots/databases/active-active-databases/global-config-tab.png differ diff --git a/static/images/rs/screenshots/databases/active-active-databases/local-config-tab.png b/static/images/rs/screenshots/databases/active-active-databases/local-config-tab.png new file mode 100644 index 0000000000..d0af82d833 Binary files /dev/null and b/static/images/rs/screenshots/databases/active-active-databases/local-config-tab.png differ diff --git a/static/images/rs/screenshots/databases/active-active-databases/local-config-tag.png b/static/images/rs/screenshots/databases/active-active-databases/local-config-tag.png new file mode 100644 index 0000000000..4b34aed9b2 Binary files /dev/null and b/static/images/rs/screenshots/databases/active-active-databases/local-config-tag.png differ diff --git a/static/images/rs/screenshots/databases/active-active-databases/local-config-warning-details.png b/static/images/rs/screenshots/databases/active-active-databases/local-config-warning-details.png new file mode 100644 index 0000000000..9f1fdd1e99 Binary files /dev/null and b/static/images/rs/screenshots/databases/active-active-databases/local-config-warning-details.png differ diff --git a/static/images/rs/screenshots/databases/active-active-databases/local-config-warning.png b/static/images/rs/screenshots/databases/active-active-databases/local-config-warning.png new file mode 100644 index 0000000000..52a6be2202 Binary files /dev/null and b/static/images/rs/screenshots/databases/active-active-databases/local-config-warning.png differ diff --git a/static/images/rs/screenshots/nodes/node-config-screen.png b/static/images/rs/screenshots/nodes/node-config-screen.png new file mode 100644 index 0000000000..d25bbeb9be Binary files /dev/null and b/static/images/rs/screenshots/nodes/node-config-screen.png differ diff --git a/static/images/rs/screenshots/nodes/node-shards.png b/static/images/rs/screenshots/nodes/node-shards.png new file mode 100644 index 0000000000..7f706772e8 Binary files /dev/null and b/static/images/rs/screenshots/nodes/node-shards.png differ diff --git a/static/images/rs/screenshots/nodes/node-stopped-service.png b/static/images/rs/screenshots/nodes/node-stopped-service.png new file mode 100644 index 0000000000..05c791f1fa Binary files /dev/null and b/static/images/rs/screenshots/nodes/node-stopped-service.png differ diff --git a/static/images/rs/screenshots/nodes/primary-node-more-actions-8-0.png b/static/images/rs/screenshots/nodes/primary-node-more-actions-8-0.png new file mode 100644 index 0000000000..ebd2b1f3cc Binary files /dev/null and b/static/images/rs/screenshots/nodes/primary-node-more-actions-8-0.png differ diff --git a/static/images/rs/screenshots/overview/active-alerts.png b/static/images/rs/screenshots/overview/active-alerts.png new file mode 100644 index 0000000000..52022ff39e Binary files /dev/null and b/static/images/rs/screenshots/overview/active-alerts.png differ diff --git a/static/images/rs/screenshots/overview/cert-expires-soon.png b/static/images/rs/screenshots/overview/cert-expires-soon.png new file mode 100644 index 0000000000..552bff262f Binary files /dev/null and b/static/images/rs/screenshots/overview/cert-expires-soon.png differ diff --git a/static/images/rs/screenshots/overview/db-status-hover.png b/static/images/rs/screenshots/overview/db-status-hover.png new file mode 100644 index 0000000000..a5e1b184b3 Binary files /dev/null and b/static/images/rs/screenshots/overview/db-status-hover.png differ diff --git a/static/images/rs/screenshots/overview/health-report-overview.png b/static/images/rs/screenshots/overview/health-report-overview.png new file mode 100644 index 0000000000..7c8c4ad949 Binary files /dev/null and b/static/images/rs/screenshots/overview/health-report-overview.png differ diff --git a/static/images/rs/screenshots/overview/running-actions.png b/static/images/rs/screenshots/overview/running-actions.png new file mode 100644 index 0000000000..b6fabd9198 Binary files /dev/null and b/static/images/rs/screenshots/overview/running-actions.png differ