Merge branch 'main' into release-rs-aug

rrelledge · rrelledge · commit 8445c147cc11 · 2024-09-04T16:44:30.000-05:00
diff --git a/content/operate/rs/clusters/add-node.md b/content/operate/rs/clusters/add-node.md
@@ -32,9 +32,9 @@ To add a node to an existing cluster:
 1. [Install the Redis Enterprise Software installation package]({{< relref "/operate/rs/installing-upgrading" >}}) on a clean installation
     of a [supported operating system]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/supported-platforms.md" >}}).
 
-1. To connect to the management UI of the new Redis Enterprise Software installation, go to: <https://URL or IP address:8443/new>
+1. To connect to the Cluster Manager UI of the new Redis Enterprise Software installation, go to: <https://URL or IP address:8443>
 
-    For example, if you installed Redis Enterprise Software on a machine with IP address 10.0.1.34, go to `https://10.0.1.34:8443/new`.
+    For example, if you installed Redis Enterprise Software on a machine with IP address 10.0.1.34, go to `https://10.0.1.34:8443`.
 
     {{< tip >}}
 The management UI uses TLS encryption with a default certificate.
diff --git a/content/operate/rs/clusters/new-cluster-setup.md b/content/operate/rs/clusters/new-cluster-setup.md
@@ -23,8 +23,8 @@ After the cluster is created you can [add multiple nodes to the cluster]({{< rel
 
 To create a cluster:
 
-1. In a browser, navigate to `https://<name or IP address of the machine with Redis Enterprise Software installed>:8443/new`.
-    For example, if you installed Redis Enterprise Software on a machine with IP address 10.0.1.34, then navigate to <https://10.0.1.34:8443/new>.
+1. In a browser, go to `https://<name or IP address of the machine with Redis Enterprise Software installed>:8443`.
+    For example, if you installed Redis Enterprise Software on a machine with IP address 10.0.1.34, go to <https://10.0.1.34:8443>.
 
     {{< note >}}
 - The management UI uses a [self-signed certificate for TLS encryption]({{< relref "/operate/rs/security/certificates/updating-certificates" >}}).
diff --git a/content/operate/rs/databases/active-active/create.md b/content/operate/rs/databases/active-active/create.md
@@ -87,7 +87,7 @@ Every instance of an Active-Active database can receive write operations, and al
         {{<image filename="images/rs/screenshots/databases/active-active-databases/create-db-add-participating-clusters.png" alt="Add cluster panel.">}}
 
         {{<note>}}
-You cannot add RAM-only clusters and [flash-enabled clusters]({{< relref "/operate/rs/databases/auto-tiering" >}}) to the same Active-Active configuration.
+If an Active-Active database [runs on flash memory]({{<relref "/operate/rs/databases/auto-tiering">}}), you cannot add participating clusters that run on RAM only.
         {{</note>}}
 
     1. Click **Join cluster** to add the cluster to the list of participating clusters. 
diff --git a/content/operate/rs/databases/active-active/manage.md b/content/operate/rs/databases/active-active/manage.md
@@ -35,7 +35,7 @@ the new database instance can accept connections and read operations.
 The new instance does not accept write operations until it is in the syncing state.
 
 {{<note>}}
-You cannot add RAM-only clusters and [flash-enabled clusters]({{< relref "/operate/rs/databases/auto-tiering" >}}) to the same Active-Active configuration.
+If an Active-Active database [runs on flash memory]({{<relref "/operate/rs/databases/auto-tiering">}}), you cannot add participating clusters that run on RAM only.
 {{</note>}}
 
 To add a new participating cluster to an existing Active-Active configuration using the Cluster Manager UI:
diff --git a/content/operate/rs/databases/active-active/planning.md b/content/operate/rs/databases/active-active/planning.md
@@ -22,7 +22,7 @@ See [Active-Active Redis]({{< relref "/operate/rs/databases/active-active/" >}})
 You need at least [two participating clusters]({{< relref "/operate/rs/clusters/new-cluster-setup" >}}) for an Active-Active database. If your database requires more than ten participating clusters, contact Redis support. You can [add or remove participating clusters]({{< relref "/operate/rs/databases/active-active/manage#participating-clusters/" >}}) after database creation.
 
 {{<note>}}
-You cannot add RAM-only clusters and [flash-enabled clusters]({{< relref "/operate/rs/databases/auto-tiering" >}}) to the same Active-Active configuration.
+If an Active-Active database [runs on flash memory]({{<relref "/operate/rs/databases/auto-tiering">}}), you cannot add participating clusters that run on RAM only.
 {{</note>}}
 
 Changes made from the Cluster Manager UI to an Active-Active database configuration only apply to the cluster you are editing. For global configuration changes across all clusters, use the `crdb-cli` command-line utility.
@@ -85,3 +85,4 @@ Active-Active databases have the following limitations:
 - The `FLUSH` command is not supported from the CLI. To flush your database, use the API or Cluster Manager UI.
 - Cross slot multi commands (such as `MSET`) are not supported with Active-Active databases.
 - The hashing policy can't be changed after database creation.
+- If an Active-Active database [runs on flash memory]({{<relref "/operate/rs/databases/auto-tiering">}}), you cannot add participating clusters that run on RAM only.
diff --git a/content/operate/rs/databases/auto-tiering/quickstart.md b/content/operate/rs/databases/auto-tiering/quickstart.md
@@ -72,7 +72,7 @@ sudo lsblk
 
 ## Set up a cluster and enable Auto Tiering
 
-1. Direct your browser to `https://localhost:8443/new` on the host machine to
+1. Direct your browser to `https://localhost:8443` on the host machine to
 see the Redis Enterprise Software Cluster Manager UI.
 
     {{<note>}}
diff --git a/content/operate/rs/databases/configure/_index.md b/content/operate/rs/databases/configure/_index.md
@@ -39,13 +39,15 @@ To edit the configuration of a database using the Cluster Manager UI:
 1. Change any [configurable database settings](#config-settings).
 
     {{< note >}}
-For [Active-Active database instances]({{< relref "/operate/rs/databases/active-active" >}}), most database settings only apply to the instance that you are editing. To manage Active-Active databases, use the legacy UI.
+For [Active-Active database instances]({{< relref "/operate/rs/databases/active-active" >}}), most database settings only apply to the instance that you are editing.
     {{< /note >}}
 
 1. Select **Save**.
 
 ## Configuration settings {#config-settings}
 
+- **Database version** - Select the Redis version when you create a database.
+
 - **Name** - The database name requirements are:
 
     - Maximum of 63 characters
@@ -102,30 +104,34 @@ You cannot enable them after database creation.
 
 ### Clustering
 
-- **Database clustering** - You can either:
-    - Enable [database clustering]({{< relref "/operate/rs/databases/durability-ha/clustering.md" >}}) and select the number of database shards.
+- **Sharding** - You can either:
+    - Turn on **Sharding** to enable [database clustering]({{< relref "/operate/rs/databases/durability-ha/clustering.md" >}}) and select the number of database shards.
 
         When database clustering is enabled, databases are subject to limitations on [Multi-key commands]({{< relref "/operate/rs/databases/durability-ha/clustering.md" >}}).
         
         You can increase the number of shards in the database at any time.
 
         You can accept the [standard hashing policy]({{< relref "/operate/rs/databases/durability-ha/clustering#standard-hashing-policy" >}}), which is compatible with Redis Community Edition, or define a [custom hashing policy]({{< relref "/operate/rs/databases/durability-ha/clustering#custom-hashing-policy" >}}) to define where keys are located in the clustered database.
 
-    - Clear the **Database clustering** option to use only one shard so that you can use [Multi-key commands]({{< relref "/operate/rs/databases/durability-ha/clustering.md" >}}) without the limitations.
+    - Turn off **Sharding** to use only one shard so that you can use [Multi-key commands]({{< relref "/operate/rs/databases/durability-ha/clustering.md" >}}) without the limitations.
 
-- Sharding
+- [**OSS Cluster API**]({{< relref "/operate/rs/databases/configure/oss-cluster-api.md" >}}) - The OSS Cluster API configuration allows access to multiple endpoints for increased throughput.
 
-- [**OSS Cluster API**]({{< relref "/operate/rs/databases/configure/oss-cluster-api.md" >}}) - {{< embed-md "oss-cluster-api-intro.md"  >}}
+    This configuration requires clients to connect to the primary node to retrieve the cluster topology before they can connect directly to proxies on each node.
+    
+    When you enable the OSS Cluster API, shard placement changes to _Sparse_, and the database proxy policy changes to _All primary shards_ automatically.
 
-    If you enable the OSS Cluster API, the shards placement policy and database proxy policy automatically change to _Sparse_ and _All master shards_.
+    {{<note>}}
+You must use a client that supports the cluster API to connect to a database that has the cluster API enabled.
+    {{</note>}}
 
-- [**Shards placement policy**]({{< relref "/operate/rs/databases/memory-performance/shard-placement-policy" >}}) - Determines how to distribute database shards across nodes in the cluster.
+- [**Shards placement**]({{< relref "/operate/rs/databases/memory-performance/shard-placement-policy" >}}) - Determines how to distribute database shards across nodes in the cluster.
 
     - _Dense_ places shards on the smallest number of nodes.
     
     - _Sparse_ spreads shards across many nodes.
 
-- [**Database proxy policy**]({{< relref "/operate/rs/databases/configure/proxy-policy" >}}) - Determines the number and location of active proxies, which manage incoming database operation requests.
+- [**Database proxy**]({{< relref "/operate/rs/databases/configure/proxy-policy" >}}) - Determines the number and location of active proxies, which manage incoming database operation requests.
 
 ### Replica Of
 
diff --git a/content/operate/rs/databases/configure/db-defaults.md b/content/operate/rs/databases/configure/db-defaults.md
@@ -124,7 +124,7 @@ To configure default shard placement, use one of the following methods:
 
 ### Database version
 
-When you create a new database, it uses the default Redis version (**Database version**) unless you specify the database version explicitly with `redis_version` in the [REST API]({{< relref "/operate/rs/references/rest-api/requests/bdbs" >}}).
+New databases use the default Redis database version unless you select a different **Database version** when you [create a database]({{<relref "/operate/rs/databases/create">}}) in the Cluster Manager UI or specify the `redis_version` in a [create database REST API request]({{< relref "/operate/rs/references/rest-api/requests/bdbs" >}}).
 
 To configure the Redis database version, use one of the following methods:
 
diff --git a/content/operate/rs/databases/create.md b/content/operate/rs/databases/create.md
@@ -15,11 +15,7 @@ Redis Enterprise Software lets you create databases and distribute them across a
 
 To create a new database:
 
-1. In your web browser, open the Cluster Manager UI of the cluster that you want to connect to in order to create the database.
-
-    - For the new Cluster Manager UI, go to `https://<hostname>:8443/new`
-
-    - For the legacy UI, go to `https://<hostname>:8443`
+1. Sign in to the Cluster Manager UI at `https://<hostname>:8443`
 
 1. Use one of the following methods to create a new database:
 
diff --git a/content/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-6-22.md b/content/operate/rs/release-notes/rs-7-4-2-releases/rs-7-4-6-22.md
@@ -74,6 +74,8 @@ Bundled Redis modules compatible with Redis database versions 6.0 and 6.2:
 
 ## Version changes
 
+- Added validation to verify the LDAP server URI contains a host and port when updating LDAP configuration.
+
 ### Product lifecycle updates
 
 #### End-of-life policy extension
