From 3f3d2e73ff7210137b35f479063feb64c9790a93 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Mon, 10 Aug 2026 11:50:57 -0500 Subject: [PATCH 1/3] Closes DOC-6953. Also covers the release-note request on RED-212186. --- .../rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md | 12 ++++++++++++ .../rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md | 12 ++++++++++++ 2 files changed, 24 insertions(+) diff --git a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md index ba36e959c4..44f5bf7626 100644 --- a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md +++ b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md @@ -193,6 +193,10 @@ openssl version If the version is earlier than 3.3.0, upgrade the `openssl` and `openssl-libs` packages before you upgrade Redis Software. +### JWT token invalidation on upgrade + +To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session (30 minutes) or token (60 minutes) to expire. + ### Reserved ports Make sure the following ports are open before upgrading Redis Software. @@ -328,6 +332,14 @@ For Active-Active databases running Redis database version 8.4, the `ACKED` opti 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. +#### Cluster Manager sign-outs and false "down" status during an Active-Active upgrade + +While an Active-Active database has participating clusters running different Redis Software versions, the Cluster Manager UI on an upgraded cluster can sign users out intermittently and show a participating cluster as down, even though replication is active and the syncers are connected. + +This affects the Cluster Manager UI only. It's caused by a JWT signing-key mismatch between nodes running different versions during the upgrade window (see [JWT token invalidation on upgrade](#jwt-token-invalidation-on-upgrade)). The data path and replication are not affected. + +To resolve it, upgrade the remaining participating clusters. The issue clears once every participating cluster runs the same version. If you're signed out, sign in again. + #### 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. diff --git a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md index 4babd2ef22..c358d1b10e 100644 --- a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md +++ b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md @@ -75,6 +75,10 @@ The following table shows which Redis modules are compatible with each Redis dat Redis Software version 8.0.16 and later requires OpenSSL 3.3 or later. +### JWT token invalidation on upgrade + +To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session (30 minutes) or token (60 minutes) to expire. + ### Reserved ports Make sure the following ports are open before upgrading Redis Software. @@ -196,6 +200,14 @@ For Active-Active databases running Redis database version 8.4, the `ACKED` opti 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. +#### Cluster Manager sign-outs and false "down" status during an Active-Active upgrade + +While an Active-Active database has participating clusters running different Redis Software versions, the Cluster Manager UI on an upgraded cluster can sign users out intermittently and show a participating cluster as down, even though replication is active and the syncers are connected. + +This affects the Cluster Manager UI only. It's caused by a JWT signing-key mismatch between nodes running different versions during the upgrade window (see [JWT token invalidation on upgrade](#jwt-token-invalidation-on-upgrade)). The data path and replication are not affected. + +To resolve it, upgrade the remaining participating clusters. The issue clears once every participating cluster runs the same version. If you're signed out, sign in again. + #### 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. From 15c1e6fa36401bdaf2e8d01f77ab67454d7f7947 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com> Date: Tue, 11 Aug 2026 13:28:49 -0500 Subject: [PATCH 2/3] Apply suggestion from @mich-elle-luna Co-authored-by: mich-elle-luna <153109578+mich-elle-luna@users.noreply.github.com> --- content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md index 44f5bf7626..080ad1e1eb 100644 --- a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md +++ b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md @@ -338,7 +338,7 @@ While an Active-Active database has participating clusters running different Red This affects the Cluster Manager UI only. It's caused by a JWT signing-key mismatch between nodes running different versions during the upgrade window (see [JWT token invalidation on upgrade](#jwt-token-invalidation-on-upgrade)). The data path and replication are not affected. -To resolve it, upgrade the remaining participating clusters. The issue clears once every participating cluster runs the same version. If you're signed out, sign in again. +To resolve it, upgrade the remaining participating clusters. The issue clears after every participating cluster runs the same version. If you're signed out, sign in again. #### Module commands limitation during Active-Active database upgrades to Redis 8.0 From b20ea7a05d2032f1201565a83130f7ddfc04f958 Mon Sep 17 00:00:00 2001 From: Kaitlyn Michael Date: Tue, 11 Aug 2026 14:03:34 -0500 Subject: [PATCH 3/3] review changes --- .../operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md | 2 +- .../operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md index 080ad1e1eb..831cbd7911 100644 --- a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md +++ b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-25.md @@ -195,7 +195,7 @@ If the version is earlier than 3.3.0, upgrade the `openssl` and `openssl-libs` p ### JWT token invalidation on upgrade -To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session (30 minutes) or token (60 minutes) to expire. +To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session or token to expire. ### Reserved ports diff --git a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md index c358d1b10e..2aa35124d6 100644 --- a/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md +++ b/content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-46.md @@ -77,7 +77,7 @@ Redis Software version 8.0.16 and later requires OpenSSL 3.3 or later. ### JWT token invalidation on upgrade -To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session (30 minutes) or token (60 minutes) to expire. +To improve system security, the JWT signing secret has changed in version 8.0.22 and later. As a result, upgrading invalidates all previously issued JWT tokens, which must be regenerated. Tokens used programmatically within the cluster are regenerated automatically. Cluster Manager users must sign out and sign in again, or wait for their session or token to expire. ### Reserved ports @@ -206,7 +206,7 @@ While an Active-Active database has participating clusters running different Red This affects the Cluster Manager UI only. It's caused by a JWT signing-key mismatch between nodes running different versions during the upgrade window (see [JWT token invalidation on upgrade](#jwt-token-invalidation-on-upgrade)). The data path and replication are not affected. -To resolve it, upgrade the remaining participating clusters. The issue clears once every participating cluster runs the same version. If you're signed out, sign in again. +To resolve it, upgrade the remaining participating clusters. The issue clears after every participating cluster runs the same version. If you're signed out, sign in again. #### Module commands limitation during Active-Active database upgrades to Redis 8.0