Skip to content

Commit cfb15ae

Browse files
RS: 7.4.6 July release docs (#484)
* DOC-3960 RS: Add replication parameter to /optimize_shards_placement API * DOC-3488 Initial/placeholder draft of RS 7.4.6 July release notes * DOC-3958 RS: Add shard_id and shard_role to GET /recover API * DOC-3488 Add enhancements and resolved issues to RS 7.4.6 July release notes * DOC-3488 Add upcoming container image OS change to release notes * DOC-3488 Feedback updates for product lifecycle updates * Apply suggestions from code review Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com> * DOC-3488 Add notes for RedisGraph EOL and RedisGears preview * DOC-3488 Rename 7.4.2 releases index to 7.4.x releases and move 7.4.6 July release notes underneath * Fix known issue RS122570 info * Update supported upgrade paths for 7.4.x and add link to product lifecycle/EOL page * Clarify known issue RS119958 only affects clusters with Auto Tiering * DOC-3488 No upgrade implications between 7.4.2 and 7.4.6 * DOC-3488 Remove rlcheck from release notes * DOC-3930 Add build number and fix outdated format and EOL in supported platforms table in release notes * Fix icons and outdated EOL in supported platforms table on release notes index page * DOC-3930 Add SHA256 checksums to release notes * DOC-3930 Rename release notes file with build number * DOC-3488 Add more details to API enhancements in release notes * DOC-3488 Feedback update for wording of recover API enhancement * DOC-3488 Feedback update for wording of API enhancements --------- Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
1 parent 94bda04 commit cfb15ae

File tree

5 files changed

+334
-13
lines changed

5 files changed

+334
-13
lines changed

content/operate/rs/installing-upgrading/upgrading/upgrade-cluster.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,13 @@ The following upgrade paths are supported:
1717

1818
| Current<br/>cluster version | Upgrade to<br/>cluster version |
1919
|:-----:|:-----:|
20-
| 7.2.x | 7.4.2 |
21-
| 6.4.x | 7.4.2<br />7.2.x |
22-
| 6.2.x | 7.4.2<br />7.2.x<br />6.4.x |
20+
| 7.2.x | 7.4.x |
21+
| 6.4.x | 7.4.x<br />7.2.x |
22+
| 6.2.x | 7.4.x<br />7.2.x<br />6.4.x |
2323
| 6.0.x | 7.2.x<br />6.4.x<br />6.2.x |
2424

25+
See the [Redis Enterprise Software product lifecycle]({{<relref "/operate/rs/installing-upgrading/product-lifecycle">}}) for more information about release numbers and the end-of-life schedule.
26+
2527
## Upgrade prerequisites
2628

2729
Before upgrading a cluster:

content/operate/rs/references/rest-api/requests/bdbs/actions/optimize_shards_placement.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,7 @@ Include query parameters in a `GET` request to generate an optimized shard place
4949
| shards_count | integer, <nobr>(range: 1-512)</nobr> (default:&nbsp;1) | Number of database server-side shards |
5050
| shards_placement | `dense` <br />`sparse` | Control the density of shards <br /> `dense`: Shards reside on as few nodes as possible <br /> `sparse`: Shards reside on as many nodes as possible |
5151
| bigstore_ram_size | integer (default:&nbsp;0) | Memory size of bigstore RAM part, expressed in bytes |
52+
| replication | `enabled`<br />`disabled` | In-memory database replication mode |
5253

5354
The following example request includes `shards_count` and `memory_size` as query parameters:
5455

content/operate/rs/references/rest-api/requests/bdbs/actions/recover.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,13 +55,21 @@ Returns a JSON object that represents the database's recovery plan, including re
5555
"data_files": [
5656
{
5757
"filename": "appendonly-1.aof",
58+
"last_modified": 1721164863.8883622,
5859
"node_uid": "1",
59-
"shard_slots": "1-2048"
60+
"shard_role": "master",
61+
"shard_slots": "1-2048",
62+
"shard_uid": "1",
63+
"size": 88
6064
},
6165
{
6266
"filename": "appendonly-2.aof",
67+
"last_modified": 1721164863.8883622,
6368
"node_uid": "2",
64-
"shard_slots": "2049-4096"
69+
"shard_role": "slave",
70+
"shard_slots": "2049-4096",
71+
"shard_uid": "2",
72+
"size": 88
6573
}
6674
],
6775
"status": "ready"

content/operate/rs/release-notes/rs-7-4-2-releases/_index.md

Lines changed: 26 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
Title: Redis Enterprise Software release notes 7.4.2
2+
Title: Redis Enterprise Software release notes 7.4.x
33
alwaysopen: false
44
categories:
55
- docs
@@ -11,7 +11,7 @@ description: New Cluster Manager UI enhancements, including Active-Active databa
1111
including for internal traffic. Maintenance mode enhancements. Module management
1212
enhancements. RHEL 9 support.
1313
hideListLinks: true
14-
linkTitle: 7.4.2 releases
14+
linkTitle: 7.4.x releases
1515
toc: 'true'
1616
weight: 70
1717
---
@@ -48,6 +48,12 @@ For more detailed release notes, select a build version from the following table
4848

4949
### Product lifecycle updates
5050

51+
#### End-of-life policy extension
52+
53+
The end-of-life policy for Redis Enterprise Software versions 6.2 and later has been extended to 24 months after the formal release of the subsequent major version. For the updated end-of-life schedule, see the [Redis Enterprise Software product lifecycle]({{<relref "/operate/rs/installing-upgrading/product-lifecycle">}}).
54+
55+
#### Supported upgrade paths
56+
5157
After August 31, 2024, Redis Enterprise Software versions 6.2.4 and 6.2.8 will not be included in [supported upgrade paths]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-cluster#supported-upgrade-paths">}}) for Redis Enterprise Software versions beyond 7.4.x. Redis Enterprise Software versions 6.2.10, 6.2.12, and 6.2.18 will continue to be part of the upgrade path.
5258

5359
The next major Redis Enterprise Software release will still bundle Redis database version 6.2 and allow database upgrades from Redis database version 6.2 to 7.x.
@@ -90,25 +96,35 @@ To prepare for the future removal of Redis 6.0:
9096

9197
- TLS 1.0 and TLS 1.1 connections, which were previously deprecated in favor of TLS 1.2 or later, are no longer supported. Verify that all clients, applications, and connections support TLS 1.2 or later.
9298

99+
### Upcoming changes
100+
101+
#### Default image change for Redis Enterprise Software containers
102+
103+
Starting with version 7.6, Redis Enterprise Software containers with the image tag `x.y.z-build` will be based on RHEL instead of Ubuntu.
104+
105+
This change will only affect you if you use containers outside the official [Redis Enterprise for Kubernetes]({{<relref "/operate/kubernetes">}}) product and use Ubuntu-specific commands.
106+
107+
To use Ubuntu-based images after this change, you can specify the operating system suffix in the image tag. For example, use the image tag `7.4.2-216.focal` instead of `7.4.2-216`.
108+
93109
### Supported platforms
94110

95111
The following table provides a snapshot of supported platforms as of this Redis Enterprise Software release. See the [supported platforms reference]({{< relref "/operate/rs/references/supported-platforms" >}}) for more details about operating system compatibility.
96112

97113
<span title="Check mark icon">&#x2705;</span> Supported – The platform is supported for this version of Redis Enterprise Software and Redis Stack modules.
98114

99-
<span title="Warning icon">&#x26A0;&#xFE0F;</span> Deprecation warning – The platform is still supported for this version of Redis Enterprise Software, but support will be removed in a future release.
115+
<span title="Warning icon" class="font-serif">:warning:</span> Deprecation warning – The platform is still supported for this version of Redis Enterprise Software, but support will be removed in a future release.
100116

101117
| Redis Enterprise<br />major versions | 7.4 | 7.2 | 6.4 | 6.2 |
102118
|---------------------------------|:-----:|:-----:|:-----:|:-----:|
103119
| **Release date** | Feb 2024 | Aug 2023 | Feb 2023 | Aug 2021 |
104-
| [**End-of-life date**]({{< relref "/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule" >}}) | Determined after<br />next major release | July 2025 | Feb 2025 | Aug 2024 |
120+
| [**End-of-life date**]({{< relref "/operate/rs/installing-upgrading/product-lifecycle#endoflife-schedule" >}}) | Determined after<br />next major release | Feb 2026 | Aug 2025 | Feb 2025 |
105121
| **Platforms** | | | | |
106122
| RHEL 9 &<br />compatible distros<sup>[1](#table-note-1)</sup> | <span title="Supported">&#x2705;</span> ||||
107123
| RHEL 8 &<br />compatible distros<sup>[1](#table-note-1)</sup> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
108-
| RHEL 7 &<br />compatible distros<sup>[1](#table-note-1)</sup> || <span title="Deprecated">&#x26A0;&#xFE0F;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
124+
| RHEL 7 &<br />compatible distros<sup>[1](#table-note-1)</sup> || <span title="Deprecated" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
109125
| Ubuntu 20.04<sup>[2](#table-note-2)</sup> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> ||
110-
| Ubuntu 18.04<sup>[2](#table-note-2)</sup> | <span title="Deprecated">&#x26A0;&#xFE0F;</span> | <span title="Deprecated">&#x26A0;&#xFE0F;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
111-
| Ubuntu 16.04<sup>[2](#table-note-2)</sup> || <span title="Deprecated">&#x26A0;&#xFE0F;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
126+
| Ubuntu 18.04<sup>[2](#table-note-2)</sup> | <span title="Deprecated" class="font-serif">:warning:</span> | <span title="Deprecated" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
127+
| Ubuntu 16.04<sup>[2](#table-note-2)</sup> || <span title="Deprecated" class="font-serif">:warning:</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
112128
| Amazon Linux 2 | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> ||
113129
| Amazon Linux 1 || <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
114130
| Kubernetes<sup>[3](#table-note-3)</sup> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> | <span title="Supported">&#x2705;</span> |
@@ -127,10 +143,12 @@ The following table provides a snapshot of supported platforms as of this Redis
127143

128144
- RS61676: Full chain certificate update fails if any certificate in the chain does not have a Common Name (CN).
129145

130-
- RS119958: The `debuginfo` script fails with the error `/bin/tar: Argument list too long` if there are too many RocksDB log files.
146+
- RS119958: The `debuginfo` script fails with the error `/bin/tar: Argument list too long` if there are too many RocksDB log files. This issue only affects clusters with Auto Tiering.
131147

132148
- RS122570: REST API `POST /crdbs` responds with a confusing error message if the cluster does not have the requested CRDB-compatible module that complies with the requested featureset.
133149

150+
This issue was fixed in [Redis Enterprise Software version 7.4.2-126]({{<relref "/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-2-126">}}).
151+
134152
- RS123142: In an Active-Active setup with at least three participating clusters, removing and re-adding a cluster after removing older clusters without re-adding them can cause missing keys and potentially lead to data loss or data inconsistency.
135153

136154
To prevent this issue, avoid adding clusters until you upgrade to the upcoming maintenance release when available.

0 commit comments

Comments
 (0)