Merge branch 'main' into release-rs-gilboa

Author: rrelledge

assets/css/index.css

@@ -598,6 +598,11 @@ html {
   scrollbar-gutter: stable;
 }
 
+/* Auto-clickable for standalone images */
+img:not(a img):not(.image-card-img):not([src*="#no-click"]) {
+  cursor: pointer;
+}
+
 /* Chroma syntax highlighting */
 
 /* Background */

content/embeds/rs-prometheus-metrics-v2.md

@@ -53,6 +53,7 @@
 | <span class="break-all">node_available_memory_no_overbooking_bytes</span> | gauge | Available RAM in the node (bytes) without taking into account overbooking |
 | node_bigstore_free_bytes | gauge | Sum of free space of back-end flash (used by flash database's [BigRedis]) on all cluster nodes (bytes); returned only when BigRedis is enabled |
 | <span class="break-all">node_cert_expires_in_seconds</span> | gauge | Certificate expiration (in seconds) per given node; read more about [certificates in Redis Enterprise]({{< relref "/operate/rs/security/certificates" >}}) and [monitoring certificates]({{< relref "/operate/rs/security/certificates/monitor-certificates" >}}) |
+| <span class="break-all">customer_managed_ine_certificates</span> | gauge | Indicates whether customer-provided internode encryption certificates are in use<br />0=No<br />1=Yes |
 | <span class="break-all">node_ephemeral_storage_avail_bytes</span> | gauge | Disk space available to RLEC processes on configured ephemeral disk (bytes) |
 | <span class="break-all">node_ephemeral_storage_free_bytes</span> | gauge | Free disk space on configured ephemeral disk (bytes) |
 | node_memory_MemFree_bytes | gauge | Free memory in the node (bytes) |

content/operate/oss_and_stack/install/archive/install-redis/install-redis-on-windows.md

@@ -41,7 +41,7 @@ sudo apt-get install redis
 Lastly, start the Redis server like so:
 
 {{< highlight bash  >}}
-sudo service redis-server start
+redis-server --daemonize yes
 {{< / highlight  >}}
 
 ### Connect to Redis

content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisbloom/redisbloom-2.8-release-notes.md

@@ -15,11 +15,22 @@ weight: 94
 
 ## Requirements
 
-RedisBloom v2.8.7 requires:
+RedisBloom v2.8.10 requires:
 
 - Minimum Redis compatibility version (database): 7.4
 - Minimum Redis Enterprise Software version (cluster): 7.8
 
+## v2.8.10 (September 2025)
+
+This is a maintenance release for RedisBloom 2.8.
+
+Update urgency: `MODERATE`: Program an upgrade of the server, but it's not urgent.
+
+Details:
+
+Bug fixes:
+- [#886](https://github.com/redisbloom/redisbloom/pull/886) - `TDIGEST.CREATE` crashes (OOM) on huge initialization values (MOD-10840).
+
 ## v2.8.7 (April 2025)
 
 This is a maintenance release for RedisBloom 2.8

content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.4-release-notes.md

@@ -17,11 +17,23 @@ weight: 97
 ---
 ## Requirements
 
-RedisJSON v2.4.12 requires:
+RedisJSON v2.4.17 requires:
 
 - Minimum Redis compatibility version (database): 6.0.16
 - Minimum Redis Enterprise Software version (cluster): 6.2.18
 
+
+## v2.4.17 (September 2025)
+
+This is a maintenance release for RedisJSON 2.4.
+
+Update urgency: `MODERATE`: Program an upgrade of the server, but it's not urgent.
+
+Details:
+
+Bug fixes
+- [#1374](https://github.com/redisjson/redisjson/pull/1374) - `JSON.DEL` doesn’t delete all matching object members / array elements (MOD-11032, MOD-11067).
+
 ## v2.4.12 (April 2025)
 
 This is a maintenance release for RedisJSON 2.4.

content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.6-release-notes.md

@@ -14,11 +14,22 @@ weight: 96
 ---
 ## Requirements
 
-RedisJSON v2.6.15 requires:
+RedisJSON v2.6.21 requires:
 
 - Minimum Redis compatibility version (database): 7.2
 - Minimum Redis Enterprise Software version (cluster): 7.2.4
 
+## v2.6.21 (September 2025)
+
+This is a maintenance release for RedisJSON 2.6.
+
+Update urgency: `MODERATE`: Program an upgrade of the server, but it's not urgent.
+
+Details:
+
+Bug fixes
+- [#1374](https://github.com/redisjson/redisjson/pull/1374) - `JSON.DEL` doesn’t delete all matching object members / array elements (MOD-11032, MOD-11067).
+
 ## v2.6.15 (April 2025)
 
 This is a maintenance release for RedisJSON 2.6.

content/operate/oss_and_stack/stack-with-enterprise/release-notes/redisjson/redisjson-2.8-release-notes.md

@@ -15,11 +15,22 @@ weight: 95
 
 ## Requirements
 
-RedisJSON v2.8.9 requires:
+RedisJSON v2.8.14 requires:
 
 - Minimum Redis compatibility version (database): 7.4
 - Minimum Redis Enterprise Software version (cluster): 7.8
 
+## v2.8.14 (September 2025)
+
+This is a maintenance release for RedisJSON 2.8.
+
+Update urgency: `MODERATE`: Program an upgrade of the server, but it's not urgent.
+
+Details:
+
+Bug fixes
+- [#1374](https://github.com/redisjson/redisjson/pull/1374) - `JSON.DEL` doesn’t delete all matching object members / array elements (MOD-11032, MOD-11067).
+
 ## v2.8.9 (April 2025)
 
 This is a maintenance release for RedisJSON 2.8.

content/operate/rs/7.8/clusters/change-node-role.md

@@ -17,7 +17,7 @@ A Redis Software cluster contains a primary node, which coordinates cluster-wide
 
 To demote the primary node to a secondary node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to promote.
+1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the primary node you want to demote.
 
     {{<image filename="images/rs/screenshots/nodes/primary-node-more-actions.png" alt="Click the more actions button for a node to access node actions.">}}
 
@@ -37,7 +37,7 @@ To demote the primary node to a secondary node using the Cluster Manager UI:
 
 To promote a secondary node to become the primary node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to promote.
+1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the secondary node you want to promote.
 
     {{<image filename="images/rs/screenshots/nodes/secondary-nodes-more-actions.png" alt="Click the more actions button for a node to access node actions.">}}
 

content/operate/rs/clusters/change-node-role.md

@@ -14,11 +14,15 @@ A Redis Software cluster contains a primary node, which coordinates cluster-wide
 
 ## Demote primary node
 
+{{< multitabs id="demote-node" 
+tab1="Cluster Manager UI"
+tab2="rladmin" >}}
+
 To demote the primary node to a secondary node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to promote.
+1. On the **Nodes** screen, click the **More actions** button (**&vellip;**) for the primary node you want to demote.
 
-    {{<image filename="images/rs/screenshots/nodes/primary-node-more-actions.png" alt="Click the more actions button for a node to access node actions.">}}
+    <img src="../../../../images/rs/screenshots/nodes/primary-node-more-actions.png" alt="Click the more actions button for a node to access node actions.">
 
 1. Select **Set as a secondary node** from the list.
 
@@ -28,20 +32,73 @@ To demote the primary node to a secondary node using the Cluster Manager UI:
 
     - **Choose specific node**: You can manually select which node becomes the new primary node.
 
-    {{<image filename="images/rs/screenshots/nodes/primary-node-set-as-secondary-dialog.png" alt="The Set as a secondary node dialog has two options to select the new primary node, either automatically or manually.">}}
+    <img src="../../../../images/rs/screenshots/nodes/primary-node-set-as-secondary-dialog.png" alt="The Set as a secondary node dialog has two options to select the new primary node, either automatically or manually.">
 
 1. Click **Confirm**.
 
+-tab-sep-
+
+To demote the primary node to a secondary node using `rladmin`:
+
+1. Identify the primary node's ID with [`rladmin cluster master`]({{<relref "/operate/rs/references/cli-utilities/rladmin/cluster/master">}}):
+
+    ```sh
+    $ rladmin cluster master
+    Node <primary-node-id> is the cluster master node
+    ```
+
+1. Run [`rladmin node enslave`]({{<relref "/operate/rs/references/cli-utilities/rladmin/node/enslave/#node-enslave">}}) with the `demote_node` option:
+
+    ```sh
+    rladmin node <primary-node-ID> enslave demote_node
+    ```
+
+    Replace `<primary-node-ID>` with the ID returned by `rladmin cluster master`.
+
+{{< /multitabs >}}
+
 ## Promote secondary node
 
+{{< multitabs id="promote-node" 
+tab1="Cluster Manager UI"
+tab2="rladmin" >}}
+
 To promote a secondary node to become the primary node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to promote.
+1. On the **Nodes** screen, click the **More actions** button (**&vellip;**) for the secondary node you want to promote.
 
-    {{<image filename="images/rs/screenshots/nodes/secondary-nodes-more-actions.png" alt="Click the more actions button for a node to access node actions.">}}
+    <img src="../../../../images/rs/screenshots/nodes/secondary-nodes-more-actions.png" alt="Click the more actions button for a node to access node actions.">
 
 1. Select **Set as the primary node** from the list.
 
 1. Click **Confirm**.
 
+
+-tab-sep-
+
+To promote a secondary node to become the primary node using `rladmin`:
+
+1. To find the IDs of secondary nodes, run [`rladmin status nodes`]({{<relref "/operate/rs/references/cli-utilities/rladmin/status#status-nodes">}}):
+
+    ```sh
+    $ rladmin status nodes
+    CLUSTER NODES:
+    NODE:ID     ROLE       ADDRESS          EXTERNAL_ADDRESS          HOSTNAME            SHARDS     CORES          FREE_RAM                 PROVISIONAL_RAM          VERSION        STATUS   
+    node:1      master     198.51.100.2                                 3d99db1fdf4b        4/100      6              14.74GB/19.54GB          10.73GB/16.02GB          7.22.0-250     OK       
+    *node:3     slave      198.51.100.4                                 b87cc06c830f        0/100      6              14.74GB/19.54GB          11.22GB/16.02GB          7.22.0-250     OK       
+    node:2      slave      198.51.100.3                                 fc7a3d332458        0/100      6              14.74GB/19.54GB          11.22GB/16.02GB          7.22.0-250     OK       
+    ```
+
+    Nodes with the `slave` role are secondary nodes.
+
+1. Run [`rladmin cluster master set`]({{<relref "/operate/rs/references/cli-utilities/rladmin/cluster/master">}}):
+
+    ```sh
+    rladmin cluster master set <secondary-node-ID>
+    ```
+
+    Replace `<secondary-node-ID>` with the ID of the secondary node you want to promote.
+
+{{< /multitabs >}}
+
 After this node becomes the primary node, all cluster management traffic is directed to it.

content/operate/rs/references/cli-utilities/rladmin/cluster/certificate.md

@@ -5,7 +5,7 @@ categories:
 - docs
 - operate
 - rs
-description: Sets the cluster certificate.
+description: Sets cluster certificates.
 headerRange: '[1-2]'
 linkTitle: certificate
 tags:
@@ -14,13 +14,14 @@ toc: 'true'
 weight: $weight
 ---
 
+## `cluster certificate set <certificate_name>`
+
 Sets a cluster certificate to a specified PEM file.
 
 ```sh
-rladmin cluster certificate
-        set <certificate name>
-        certificate_file <certificate filepath>
-        [ key_file <key filepath> ]
+rladmin cluster certificate set <certificate_name>
+        certificate_file <filepath>
+        [ key_file <filepath> ]
 ```
 
 To set a certificate for a specific service, use the corresponding certificate name. See the [certificates table]({{< relref "/operate/rs/security/certificates" >}}) for the list of cluster certificates and their descriptions.
@@ -29,7 +30,7 @@ To set a certificate for a specific service, use the corresponding certificate n
 
 | Parameter | Type/Value | Description |
 |-----------|------------|-------------|
-| certificate name | 'cm'<br /> 'api'<br /> 'proxy'<br /> 'syncer'<br /> 'metrics_exporter' | Name of the certificate to update |
+| certificate_name | 'cm'<br /> 'api'<br /> 'proxy'<br /> 'syncer'<br /> 'metrics_exporter' | Name of the certificate to update. See the [certificates table]({{< relref "/operate/rs/security/certificates" >}}) for descriptions. |
 | certificate_file | filepath | Path to the certificate file |
 | key_file | filepath | Path to the key file (optional) |
 
@@ -39,8 +40,47 @@ Reports that the certificate was set to the specified file. Returns an error mes
 
 ### Example
 
+Update the proxy certificate:
+
 ```sh
 $ rladmin cluster certificate set proxy \
        certificate_file /tmp/proxy.pem
 Set proxy certificate to contents of file /tmp/proxy.pem
 ```
+
+## `cluster certificate set internal`
+
+Sets [customer-provided internode encryption certificates]({{<relref "/operate/rs/security/encryption/internode-encryption#customer-provided-certificates">}}).
+
+```sh
+rladmin cluster certificate set internal
+        dpine_certificate_file <filepath>
+        dpine_key_file <filepath>
+        cpine_certificate_file <filepath>
+        cpine_key_file <filepath>
+```
+
+### Parameters
+
+| Parameter | Type/Value | Description |
+|-----------|------------|-------------|
+| dpine_certificate_file | filepath | Path to the data plane internode encryption (DPINE) certificate file |
+| dpine_key_file | filepath | Path to the data plane internode encryption (DPINE) key file |
+| cpine_certificate_file | filepath | Path to the control plane internode encryption (CPINE) certificate file |
+| cpine_key_file | filepath | Path to the control plane internode encryption (CPINE) key file |
+
+### Returns
+
+Reports that the internal certificates were set to the specified files. Returns an error message if the certificates fail to update.
+
+### Example
+
+Set up [customer-provided internode encryption certificates]({{<relref "/operate/rs/security/encryption/internode-encryption#customer-provided-certificates">}}):
+
+```sh
+$ rladmin cluster certificate set internal \
+       dpine_certificate_file /tmp/dpine_cert.pem \
+       dpine_key_file /tmp/dpine_key.pem \
+       cpine_certificate_file /tmp/cpine_cert.pem \
+       cpine_key_file /tmp/cpine_key.pem
+```