RS 8.0.20 June maintenance release notes

content/operate/rs/references/cli-utilities/rladmin/tune.md

@@ -285,7 +285,7 @@ rladmin tune proxy { <id> | all }
 |-----------------|----------------------------|-------------------------------------------------------------------------------------|
 | id              | integer                    | ID of the specified proxy                                                           |
 | all             |                            | Configures settings for all proxies                                                 |
-| client_eviction | boolean (default: false) | If `true,`, enables client eviction based on `maxmemory_clients`. |
+| client_eviction | boolean (default: true) | If `true`, enables client eviction based on `maxmemory_clients`. |
 | incoming_connections_capacity | integer (default: 0) | The maximum number of concurrent incoming connections, also known as the maximum burst size. The default is 0, which means no limit. |
 | incoming_connections_min_capacity | integer (default: 10) | The minimum number of free slots required before accepting new connections after an overflow. |
 | incoming_connections_rate_limit | integer (default: 0) | The maximum number of incoming connections per second. The default is 0, which means no limit. |

content/operate/rs/references/rest-api/objects/proxy.md

@@ -16,7 +16,7 @@ An API object that represents a [proxy](https://en.wikipedia.org/wiki/Proxy_serv
 |------|------------|-------------|
 | uid | integer | Unique ID of the proxy (read-only) |
 | backlog | integer | TCP listen queue backlog |
-| client_eviction | boolean (default: false) | If `true,`, enables client eviction based on `maxmemory_clients`. |
+| client_eviction | boolean (default: true) | If `true`, enables client eviction based on `maxmemory_clients`. |
 | client_keepcnt | integer | Client TCP keepalive count |
 | client_keepidle | integer | Client TCP keepalive idle |
 | client_keepintvl | integer | Client TCP keepalive interval |

content/operate/rs/release-notes/rs-8-0-releases/_index.md

@@ -121,7 +121,11 @@ Redis Software version 8.0.16 and later requires OpenSSL 3.3 or later.
 
 Make sure the following ports are open before upgrading Redis Software.
 
-Ports reserved as of Redis Software version 8.0.18:
+The following port was added as a reserved port in Redis Software version 8.0.18; however, it is optional instead of reserved in Redis Software version 8.0.20-44:
+
+| Port | Process name | Usage |
+|------|--------------|-------|
+| 3357 | reconciliation_tree_grpc | Internal communication |
 
 | Port | Process name | Usage | 
 |------|--------------|-------|
@@ -221,6 +225,8 @@ The following table provides a snapshot of supported platforms as of this Redis
 
 - RS196225: After upgrading to Redis Software version 8.0.x, previously working LDAP filters that use an `OR` clause to match multiple attributes can fail to find a unique DN for some users.
 
+    This issue was fixed in Redis Software version 8.0.20-44.
+
 - RS193156: Active Directory LDAP authentication can fail in the Cluster Manager UI after upgrading to Redis Software version 8.0.16-33 due to an issue with LDAP TLS client certificate handling. Users previously authenticated through Active Directory can no longer sign in to the Cluster Manager UI after the upgrade.
 
     As a workaround, configure an LDAP client certificate using an [update cluster certificates]({{<relref "/operate/rs/references/rest-api/requests/cluster/certificates">}}) REST API request:
@@ -254,6 +260,10 @@ The following table provides a snapshot of supported platforms as of this Redis
 
 ## Known limitations
 
+#### Redis Search query failures during rolling upgrades across the 8.4 version boundary
+
+Redis Search queries can fail during a rolling upgrade when a cluster contains shards running Redis versions earlier than 8.4 and shards running Redis version 8.4 or later, due to an internal protocol change introduced in version 8.4. This issue affects only clusters where `parallel_shards_upgrade` has been changed from its default value of `0`. If both conditions apply, expect Redis Search downtime until all nodes are upgraded.
+
 #### 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.