diff --git a/content/rc/changelog/march-2024.md b/content/rc/changelog/march-2024.md index 10106a33643..f323192fb26 100644 --- a/content/rc/changelog/march-2024.md +++ b/content/rc/changelog/march-2024.md @@ -13,4 +13,8 @@ aliases: [] ### Fixed subscriptions through Google Cloud Marketplace -You can now use your [Google Cloud Marketplace]({{}}) account to pay for your Fixed subscriptions as well as your Flexible subscriptions. \ No newline at end of file +You can now use your [Google Cloud Marketplace]({{}}) account to pay for your Fixed subscriptions as well as your Flexible subscriptions. + +### Active-Passive with TLS + +[Active-Passive]({{}}) now supports source databases that require connections over TLS. See [Migrate data]({{}}) for more information. \ No newline at end of file diff --git a/content/rc/databases/migrate-databases.md b/content/rc/databases/migrate-databases.md index b615d5b5251..169cefdbe81 100644 --- a/content/rc/databases/migrate-databases.md +++ b/content/rc/databases/migrate-databases.md @@ -52,48 +52,70 @@ To migrate data using Active-Passive syncing, specify the target database as an {{< note >}} Before you use Active-Passive, be aware of the following limitations: -- An error will appear when syncing the two databases if the source database has [Transport Layer Security (TLS)]({{< relref "/rc/security/database-security/tls-ssl" >}}) enabled. [Contact support](https://redis.com/company/support/) if you want to migrate a TLS-enabled database using Active-Passive. - An error will appear when syncing the two databases if the source and target databases are hosted on different Redis Cloud accounts. [Contact support](https://redis.com/company/support/) if you want to migrate a database between accounts using Active-Passive. + - As long as Active-Passive is enabled, data in the target database will not expire and will not be evicted regardless of the set [data eviction policy]({{}}). We recommend that you turn off Active-Passive after the databases are synced. {{< /note >}} ### Detailed Active-Passive syncing process -If the databases belong to the same Redis Cloud account, follow these detailed steps to migrate data using Active-Passive syncing: +Follow these detailed steps to migrate data using Active-Passive syncing: + +1. Select **Databases** from the [Redis Cloud console](https://app.redislabs.com/) menu and select the target database in the list. -1. Select **Databases** from the [Redis Cloud console](https://app.redislabs.com/) menu and select the source database in the list. + {{Select the target database from the database list.}}{{< /image >}} - {{Select the source database from the database list.}}{{< /image >}} +4. From the **Configuration** tab of the target database, select **Edit database**. -2. Select the **Copy** button next to the **Public endpoint** details for the source database to copy the endpoint details to the Clipboard. + {{Use the **Edit Database** button to change the configuration of the target database.}}{{< /image >}} - {{The Copy button copies the public endpoint details to the Clipboard.}}{{< /image >}} +5. In the **Durability** section, enable **Active-Passive Redis** and then select **Add Source**. -3. Use the database list drop-down to select the target database. + {{Active-Passive settings are located in the **Durability** section of the database **Configuration** tab.}}{{< /image >}} - {{Use the database list drop-down to select the target database.}}{{< /image >}} + {{Use the **Add Source** button to specify the source of the Active-Passive replica.}}{{< /image >}} -4. From the **Configuration** tab of the target database, select **Edit database**. +6. This will open the **Add Active-Passive Redis** screen. Select where the source database is located. - {{Use the **Edit Database** button to change the configuration of the target database.}}{{< /image >}} + {{The Add Active-Passive Redis screen.}}{{< /image >}} -5. In the **Durability** section, enable **Active-Passive Redis** and then select **Add URI**. + - Select **Current account** if the source database is located in this Redis Cloud account. + + Select the source database from the **Source database** list. You can type in the database's name to find it. - {{Active-Passive settings are located in the **Durability** section of the database **Configuration** tab.}}{{< /image >}} + {{Select the Source database from the database list.}}{{< /image >}} + + - If the source database is hosted externally, select **External**. + + 1. In the **Enter the source URI** field, type `redis://` and then paste in the public endpoint details. + + {{The source URI must be specified using the 'redis://' protocol.}}{{< /image >}} + + 1. Select if the source database requires Transport Layer Security (TLS). + + - If the source database requires TLS, select **TLS** and enter the public server certificate in the **Server Certificate** field. + + {{The Server Certificate field.}}{{< /image >}} + + - If the source database requires client authentication, select **Mutual TLS**. + + 1. Enter the public server certificate in the **Server Certificate** field. + + {{The Server Certificate field.}}{{< /image >}} - {{Use the **Add URI** button to specify the source of the Active-Passive replica.}}{{< /image >}} + 1. Select **Download** to download the client certificate. -6. In the text box, type `redis://` and then paste in the public endpoint details. + {{The Client Certificate field. Select Download to download the client certificate.}}{{< /image >}} - {{The source URI must be specified using the 'redis://' protocol.}}{{< /image >}} + 1. Configure the source database to accept the client certificate. - Select **Save** to make sure you've specified the source URI correctly. +7. Select **Save Active-Passive** to save your Active-Passive settings. - {{The **Save** button verifies the Source URI and you can't save until it validates.}}{{< /image >}} + {{The **Save** button verifies the Source URI and you can't save until it validates.}}{{< /image >}} - If the endpoint cannot be verified, make sure that you've copied the details directly from the source database and that the value you entered starts with `redis://`. + For an external database, Redis will verify the endpoint at this step. If the endpoint cannot be verified, make sure that you've copied the details directly from the source database and that the value you entered starts with `redis://`. -7. Select **Save Database** to begin updating the database. +8. Select **Save Database** to begin updating the database. {{Use the **Save Database** button to save your changes, deploy the database, and to start data migration.}}{{< /image >}} diff --git a/content/rc/subscriptions/create-fixed-subscription.md b/content/rc/subscriptions/create-fixed-subscription/_index.md similarity index 64% rename from content/rc/subscriptions/create-fixed-subscription.md rename to content/rc/subscriptions/create-fixed-subscription/_index.md index c56dfc38b2d..53792bfe0de 100644 --- a/content/rc/subscriptions/create-fixed-subscription.md +++ b/content/rc/subscriptions/create-fixed-subscription/_index.md @@ -18,7 +18,7 @@ If you're new to Redis Cloud, the [quick start]({{}}). The 30 MB Fixed plan is free; it's designed for learning and building test projects. It gives you enough space to learn Redis concepts and develop application prototypes. @@ -26,33 +26,7 @@ Our paid plans start at 250 MB and offer extra features, like high availability If you need additional resources, you can [upgrade your subscription]({{}}) at any time. -There are some differences between plans for the different high availability options. See the tables for [No replication and single-zone replication](#cache-standard) and [Multi-zone replication](#multi-az) for more details. - -### No replication and single-zone replication {#cache-standard} - -| **DB size**[1](#table-note-1-cache-standard) | **30 MB (Free)** | **250 MB** | **1 GB** | **2.5 GB** | **5 GB** | **12 GB** | -|---|---|---|---|---|---|---| -| **Concurrent
connections
per database** | 30 | 256 | 1024 | 2500 | 5000 | 10000 | -| **CIDR
allow rules** | 1 | 4 | 4-8 | 4-8 | 4-16 | 4-32 | -| **Monthly
total network
bandwidth** | 5 GB | 100 GB | 200 GB | 400 GB | 800 GB | 2000 GB | -| **Maximum
throughput[2](#table-note-2-cache-standard)** | 100 ops/sec | 1000 ops/sec | 2000 ops/sec | 4000 ops/sec | 8000 ops/sec | 16000 ops/sec | - -1. Database size includes replication where applicable. See [High availability cost impact]({{}}) for more information. - -2. Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024. - -### Multi-zone replication {#multi-az} - -| **DB size **[1](#table-note-1-multi-az) | **250 MB** | **1 GB** | **2.5 GB** | **5 GB** | **12 GB** | -|---|---|---|---|---|---| -| **Concurrent
connections
per database** | 256 | 1024 | 2500 | 5000 | 10000 | -| **CIDR
allow rules** | 4 | 8 | 8 | 16 | 32 | -| **Monthly
total network
bandwidth** | 64 GB | 200 GB | 400 GB | 800 GB | 2000 GB | -| **Maximum
throughput[2](#table-note-2-multi-az)** | 1000 ops/sec | 2000 ops/sec | 4000 ops/sec | 8000 ops/sec | 16000 ops/sec | - -1. Database size includes replication. See [High availability cost impact]({{}}) for more information. - -2. Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024. +There are some differences between plans for the various high availability options. See [Fixed plan details]({{}}) for more information. ## Create a Fixed subscription diff --git a/content/rc/subscriptions/create-fixed-subscription/fixed-plan-details.md b/content/rc/subscriptions/create-fixed-subscription/fixed-plan-details.md new file mode 100644 index 00000000000..fec470e8921 --- /dev/null +++ b/content/rc/subscriptions/create-fixed-subscription/fixed-plan-details.md @@ -0,0 +1,38 @@ +--- +Title: Fixed plan details +description: Provides detailed information on Fixed plans +weight: $weight +alwaysopen: false +categories: ["RC"] +--- + +## Current Fixed plans + +These plans are currently offered for all new and upgraded Fixed subscriptions (updated March 2024). + +| **DB size**[1](#table-note-1) | **30 MB (Free)** | **250 MB** | **1 GB** | **2.5 GB** | **5 GB** | **12 GB** | +|---|---|---|---|---|---|---| +| **Concurrent
connections
per database** | 30 | 256 | 1024 | 2500 | 5000 | 10000 | +| **CIDR
allow rules** | 1 | 4 | 4-8 | 4-8 | 4-16 | 4-32 | +| **Monthly
total network
bandwidth** | 5 GB | 100 GB | 200 GB | 400 GB | 800 GB | 2000 GB | +| **Maximum
throughput[2](#table-note-2)** | 100 ops/sec | 1000 ops/sec | 2000 ops/sec | 4000 ops/sec | 8000 ops/sec | 16000 ops/sec | + +1. Database size includes replication where applicable. See [High availability cost impact]({{}}) for more information. + +2. Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024. + +## Previous plans {#legacy} + +These plans were available before November 2023. + +{{}} +| **Max DB size **[1](#table-note-1-legacy) | **30 MB** | **100 MB** | **250 MB** | **500 MB** | **1 GB** | **2.5 GB** | **5 GB** | **10 GB** | +|-----------------------------------------------------------------------------------|------------------|------------------|-------------------|-------------------|-------------------|-------------------|-------------------|--------------------| +| **Concurrent
connections
per database** | 30 | 256 | 256 | 512 | 1024 | 2500 | 5000 | 10000 | +| **Monthly
total network
bandwidth**[2](#table-note-2-legacy) | 5 GB | 50 GB | 100 GB | 150 GB | 200 GB | 400 GB | 800 GB | 2000 GB | +| **Maximum
throughput** | 100 ops/sec | 500 ops/sec | 1000 ops/sec | 1500 ops/sec | 2000 ops/sec | 4000 ops/sec | 8000 ops/sec | 16000 ops/sec | +{{}} + +1. Database size includes replication. See [High availability cost impact]({{}}) for more information. + +2. Assumes request size of 1 KiB. Maximums are capped by actual MB/s reached. To find the MB/s limit, divide the Maximum throughput by 1024. \ No newline at end of file diff --git a/content/rc/subscriptions/maintenance/_index.md b/content/rc/subscriptions/maintenance/_index.md index 64f04c3fce4..91d4ac7d05d 100644 --- a/content/rc/subscriptions/maintenance/_index.md +++ b/content/rc/subscriptions/maintenance/_index.md @@ -10,9 +10,9 @@ categories: [] aliases: --- -Redis will maintain your Redis Cloud subscriptions and databases as needed to ensure your databases are running the most stable and up-to-date version of Redis. During maintenance, you may notice some latency when connecting to your databases. +Redis will maintain your Redis Cloud subscriptions and databases as needed to ensure your databases are running the most stable and up-to-date version of Redis. -Redis will attempt to perform maintenance during low-traffic hours when possible, based on the region where your subscription is located. If you want to control when Redis can perform maintenance for a Redis Cloud Pro subscription, you can [set manual maintenance windows]({{}}). +By default, Redis will perform maintenance automatically while limiting service disruption as much as possible. If you want to control when Redis can perform maintenance for a Redis Cloud Pro subscription, you can [set manual maintenance windows]({{}}). ## Maintenance activities @@ -26,15 +26,34 @@ This includes, but is not limited to: - Adding more memory to a node - Applying security patches -Redis will notify users by email when maintenance starts and ends. If Redis needs an action from a user to start maintenance, Redis will notify users with a reasonable amount of time before planned maintenance. +Redis will notify users by email when maintenance starts and ends. For more details, see [Notifications](#notifications). -For major upgrades or upgrades that might include breaking changes, users will receive an advance notification with sufficient time to prepare before the upgrade. +During maintenance, your database will be operational, but you may notice some latency when connecting to your databases. -If you want to receive notifications by email, make sure **Operational emails** are activated in your user settings in [Access Management]({{}}). +Your application may also disconnect from your database for a few seconds. Most Redis clients are set to refresh their DNS address when they reconnect to the database, and you will not be required to perform any further action. If you encounter connectivity problems for more than a minute during maintenance, please refresh your DNS entries. ### Urgent maintenance Urgent maintenance refers to any activity that could affect service and cannot wait for scheduling. This includes applying urgent security patches. -Redis can perform urgent maintenance at any time, even if you have set a manual maintenance window or have temporarily skipped maintenance. Redis will notify users by email when urgent maintenance starts and ends. +Redis can perform urgent maintenance at any time, even if you have set a manual maintenance window or have temporarily [skipped maintenance]({{}}). Redis will notify you by email when urgent maintenance starts and ends. +## Notifications + +Redis will notify you by email when maintenance starts and ends. If Redis needs an action from you to start maintenance, Redis will notify you with a reasonable amount of time before planned maintenance. + +For major upgrades or upgrades that might include breaking changes, you will receive an advance notification with sufficient time to prepare before the upgrade. + +If you want to receive maintenance notifications by email: + +1. Go to [Access Management]({{}}) and select your account in the list. + +1. Select the Edit button. + + {{Use the Edit button change details for a team member.}}{{< /image >}} + +1. Select **Operational emails** if it is not already turned on. + + {{Use the Edit User dialog to change the details for a user}}{{< /image >}} + +1. Select **Save user** to save your changes. \ No newline at end of file diff --git a/content/rc/subscriptions/maintenance/set-maintenance-windows.md b/content/rc/subscriptions/maintenance/set-maintenance-windows.md index 360877e3f2e..830bd5747fe 100644 --- a/content/rc/subscriptions/maintenance/set-maintenance-windows.md +++ b/content/rc/subscriptions/maintenance/set-maintenance-windows.md @@ -13,7 +13,7 @@ aliases: /rc/subscriptions/maintenance/set-maintenance-windows By default, Redis will maintain your Redis Cloud subscriptions and databases as needed. During maintenance, you may notice some latency when connecting to your databases. For more information about the types of maintenance and how Redis maintains your subscriptions, see [Maintenance]({{}}). -You typically do not need to set a maintenance window manually as Redis will attempt to perform maintenance during low-traffic hours when possible, based on the region where your subscription is located. If you want to control when Redis performs maintenance for a Redis Cloud Pro subscription, you can [set manual maintenance windows](#set-manual-maintenance-windows) to ensure non-urgent maintenance will occur at set times. Configuring or altering the maintenance window will not have any impact on your subscription or databases. +By default, Redis will perform maintenance automatically while limiting service disruption as much as possible. If you want to control when Redis performs maintenance for a Redis Cloud Pro subscription, you can [set manual maintenance windows](#set-manual-maintenance-windows) to ensure non-urgent maintenance will occur at set times. Configuring or altering the maintenance window will not have any impact on your subscription or databases. ## Set manual maintenance windows diff --git a/content/rc/subscriptions/upgrade-fixed-flexible.md b/content/rc/subscriptions/upgrade-fixed-flexible.md index 3fc043c8e68..e8e0eacfad9 100644 --- a/content/rc/subscriptions/upgrade-fixed-flexible.md +++ b/content/rc/subscriptions/upgrade-fixed-flexible.md @@ -45,8 +45,6 @@ You can migrate your Redis Cloud Essentials database to your new Redis Cloud Pro {{< note >}} Before you follow this guide, be aware of the following limitations: -- If your Redis Cloud Essentials database has [Transport Layer Security (TLS)]({{< relref "/rc/security/database-security/tls-ssl" >}}) enabled, you won't be able to migrate your database between subscriptions using this guide. Use the [Transfer via import]({{}}) method or [contact support](https://redis.com/company/support/) if you want to migrate a TLS-enabled database using Active-Passive. - - This guide is for migrating databases between subscriptions in the same Redis Cloud console account. [Contact support](https://redis.com/company/support/) if you want to migrate a database between accounts using Active-Passive. - As long as Active-Passive is enabled, data in the target database will not expire and will not be evicted regardless of the set [data eviction policy]({{}}). We recommend that you turn off Active-Passive after the databases are synced. @@ -58,11 +56,17 @@ Before you follow this guide, be aware of the following limitations: {{The Edit database button lets you change selected database properties.}}{{< /image >}} -1. In the **Durability** section, enable **Active-Passive Redis** and then select **Add Account's Path**. +1. In the **Durability** section, enable **Active-Passive Redis** and then select **Add Source**. + + {{Active-Passive settings are located in the **Durability** section of the database **Configuration** tab.}}{{< /image >}} + + {{Use the **Add Source** button to specify the source of the Active-Passive replica.}}{{< /image >}} + +1. This will open the **Add Active-Passive Redis** screen. Select **Current account** to connect a database in your current account. - {{Use the Add Account's Path button to specify the source of the Active-Passive replica.}}{{< /image >}} + {{The Add Active-Passive Redis screen.}}{{< /image >}} -1. Select your Redis Cloud Essentials database from the list. This will be your source database. You can type in the database's name to find it. +1. Select your Redis Cloud Essentials database from the **Source database** list. This will be your source database. You can type in the database's name to find it. {{Select the Source database from the database list.}}{{< /image >}} diff --git a/content/rdi/_index.md b/content/rdi/_index.md index 03c2c7f5e37..6ca987f92a5 100644 --- a/content/rdi/_index.md +++ b/content/rdi/_index.md @@ -52,6 +52,7 @@ RDI supports the following database sources using [Debezium Server](https://debe | Google Cloud SQL MySQL | 8.0 || | Google Cloud SQL Postgres | 15 || | Google Cloud SQL SQL Server | 2019 || +| Google Cloud AlloyDB for PostgreSQL | || ## Supported targets (write-behind) diff --git a/content/rs/clusters/cluster-recovery.md b/content/rs/clusters/cluster-recovery.md index cb19efd7d52..86a1e757624 100644 --- a/content/rs/clusters/cluster-recovery.md +++ b/content/rs/clusters/cluster-recovery.md @@ -16,7 +16,7 @@ When a Redis Enterprise Software cluster fails, you must use the cluster configuration file and database data to recover the cluster. {{< note >}} -For cluster recovery in a Kubernetes deployment, go to: [Recover a Redis Enterprise cluster on Kubernetes]({{< relref "/kubernetes/re-clusters/cluster-recovery.md" >}}). +For cluster recovery in a Kubernetes deployment, see [Recover a Redis Enterprise cluster on Kubernetes]({{< relref "/kubernetes/re-clusters/cluster-recovery" >}}). {{< /note >}} Cluster failure can be caused by: @@ -24,15 +24,14 @@ Cluster failure can be caused by: - A hardware or software failure that causes the cluster to be unresponsive to client requests or administrative actions. - More than half of the cluster nodes lose connection with the cluster, resulting in quorum loss. -To recover a cluster and re-create it as it was before the failure -you must restore the cluster configuration (ccs-redis.rdb) to the cluster nodes. -To restore the data that was in the databases to databases in the new cluster -you must restore the database persistence files (backup, AOF, or snapshot files) to the databases. +To recover a cluster and re-create it as it was before the failure, +you must restore the cluster configuration `ccs-redis.rdb` to the cluster nodes. +To recover databases in the new cluster, you must restore the databases from persistence files such as backup files, append-only files (AOF), or RDB snapshots. These files are stored in the [persistent storage location]({{< relref "/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}). The cluster recovery process includes: -1. Install RS on the nodes of the new cluster. +1. Install Redis Enterprise Software on the nodes of the new cluster. 1. Mount the persistent storage with the recovery files from the original cluster to the nodes of the new cluster. 1. Recover the cluster configuration on the first node in the new cluster. 1. Join the remaining nodes to the new cluster. @@ -45,23 +44,21 @@ The cluster recovery process includes: make sure there are no Redis processes running on any nodes in the new cluster. - We recommend that you use clean persistent storage drives for the new cluster. If you use the original storage drives, - make sure that you backup the files on the original storage drives to a safe location. + make sure you back up the files on the original storage drives to a safe location. - Identify the cluster configuration file that you want to use as the configuration for the recovered cluster. The cluster configuration file is `/css/ccs-redis.rdb` on the persistent storage for each node. -## Recovering the cluster +## Recover the cluster -1. (Optional) If you want to recover the cluster to the original cluster nodes, uninstall RS from the nodes. +1. (Optional) If you want to recover the cluster to the original cluster nodes, uninstall Redis Enterprise Software from the nodes. -1. Install [RS]({{< relref "/rs/installing-upgrading" >}}) on the new cluster nodes. - - Do not configure the cluster nodes (`rladmin cluster create` in the CLI or **Setup** in the admin console). +1. [Install Redis Enterprise Software]({{< relref "/rs/installing-upgrading/install/install-on-linux" >}}) on the new cluster nodes. The new servers must have the same basic hardware and software configuration as the original servers, including: - The same number of nodes - At least the same amount of memory - - The same RS version + - The same Redis Enterprise Software version - The same installation user and paths {{< note >}} @@ -78,31 +75,12 @@ of the configuration and persistence files on each of the nodes. If you use local persistent storage, place all of the recovery files on each of the cluster nodes. -1. To recover the cluster configuration from the original cluster to the first node in the new cluster, - from the [`rladmin`]({{}}) command-line interface (CLI): +1. To recover the original cluster configuration, run [`rladmin cluster recover`]({{}}) on the first node in the new cluster: ```sh rladmin cluster recover filename [ | ] node_uid rack_id ``` - {{% expand "Command syntax" %}} -`` - The full path of the old cluster configuration file in the persistent storage. -The cluster configuration file is `/css/ccs-redis.rdb`. - -`` - The id of the node, in this case `1`. - -`` (optional) - The location of the [persistent storage ]({{< relref "/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) -in the new node. - -`` (optional) - The location of the [ephemeral storage]({{< relref "/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) -in the new node. - -`` (optional) - If [rack-zone awareness]({{< relref "/rs/clusters/configure/rack-zone-awareness.md" >}}) -was enabled in the cluster, -you can use this parameter to override the rack ID value that was set for the node with ID 1 with a new rack ID. -Otherwise, the node gets the same rack ID as the original node. - {{% /expand %}} - For example: ```sh @@ -112,44 +90,23 @@ Otherwise, the node gets the same rack ID as the original node. When the recovery command succeeds, this node is configured as the node from the old cluster that has ID 1. -1. To join the remaining servers to the new cluster, run `rladmin cluster join` from each new node: +1. To join the remaining servers to the new cluster, run [`rladmin cluster join`]({{}}) from each new node: ```sh - rladmin cluster join [ nodes | name ] username password replace_node + rladmin cluster join nodes username password replace_node ``` - {{% expand "Command syntax" %}} -`nodes` - The IP address of a node in the cluster that this node is joining. - -`name` - The [FQDN name]({{< relref "/rs/networking/cluster-dns" >}}) -of the cluster this node is joining. - -`username` - The email address of the cluster administrator. - -`password` - The password of the cluster administrator. - -`replace_node` - The ID of the node that this node replaces from the old cluster. - -`persistent_path` (optional) - The location of the [persistent storage]({{< relref "/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) -in the new node. - -`ephemeral_path` (optional) - The location of the [ephemeral storage]({{< relref "/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}) -in the new node. - -`rack_id` (optional) - If [rack-zone awareness]({{< relref "/rs/clusters/configure/rack-zone-awareness.md" >}}) was enabled in the cluster, -use this parameter to set the rack ID to be the same as the rack ID -of the old node. You can also change the value of the rack ID by -providing a different value and using the `override_rack_id` flag. - {{% /expand %}} - For example: ```sh rladmin cluster join nodes 10.142.0.4 username admin@example.com password mysecret replace_node 2 ``` - You can run the `rladmin status` command to verify that the recovered nodes are now active, - and that the databases are pending recovery. +1. Run [`rladmin status`]({{}}) to verify the recovered nodes are now active and the databases are pending recovery: + + ```sh + rladmin status + ``` {{< note >}} Make sure that you update your [DNS records]({{< relref "/rs/networking/cluster-dns" >}}) diff --git a/content/rs/databases/active-active/create.md b/content/rs/databases/active-active/create.md index 4b17e2b746d..6ccbc6ac9af 100644 --- a/content/rs/databases/active-active/create.md +++ b/content/rs/databases/active-active/create.md @@ -91,6 +91,10 @@ Every instance of an Active-Active database can receive write operations, and al {{Add cluster panel.}}{{}} + {{}} +You cannot add RAM-only clusters and [flash-enabled clusters]({{}}) to the same Active-Active configuration. + {{}} + 1. Click **Join cluster** to add the cluster to the list of participating clusters. 1. Enter a **Database name**. diff --git a/content/rs/databases/active-active/manage.md b/content/rs/databases/active-active/manage.md index 46f9ea07687..99f88a7fc21 100644 --- a/content/rs/databases/active-active/manage.md +++ b/content/rs/databases/active-active/manage.md @@ -40,6 +40,10 @@ After you add new participating clusters to an existing Active-Active database, 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. +{{}} +You cannot add RAM-only clusters and [flash-enabled clusters]({{}}) to the same Active-Active configuration. +{{}} + To add a new participating cluster to an existing Active-Active configuration using the Cluster Manager UI: 1. Select the Active-Active database from the **Databases** list and go to its **Configuration** screen. diff --git a/content/rs/databases/active-active/planning.md b/content/rs/databases/active-active/planning.md index 7a7e8f8d26e..db9e0bb1aec 100644 --- a/content/rs/databases/active-active/planning.md +++ b/content/rs/databases/active-active/planning.md @@ -21,7 +21,11 @@ See [Active-Active Redis]({{}}) for more ## Participating clusters -For Active-Active databases, you need to [set up your participating clusters]({{}}). At least two participating clusters. If your database requires more than ten participating clusters, contact Redis support. You can [add or remove participating clusters]({{}}) after database creation. +You need at least [two participating clusters]({{}}) for an Active-Active database. If your database requires more than ten participating clusters, contact Redis support. You can [add or remove participating clusters]({{}}) after database creation. + +{{}} +You cannot add RAM-only clusters and [flash-enabled clusters]({{}}) to the same Active-Active configuration. +{{}} Changes made from the admin console 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. diff --git a/static/images/rc/button-database-uri-add.png b/static/images/rc/button-database-uri-add.png old mode 100755 new mode 100644 index 2bdafc3496d..e221f3ba704 Binary files a/static/images/rc/button-database-uri-add.png and b/static/images/rc/button-database-uri-add.png differ diff --git a/static/images/rc/database-add-account-path-list.png b/static/images/rc/database-add-account-path-list.png index f286c58edca..22ed16ec11c 100644 Binary files a/static/images/rc/database-add-account-path-list.png and b/static/images/rc/database-add-account-path-list.png differ diff --git a/static/images/rc/icon-database-save-active-passive.png b/static/images/rc/icon-database-save-active-passive.png new file mode 100644 index 00000000000..b6b7ddbce96 Binary files /dev/null and b/static/images/rc/icon-database-save-active-passive.png differ diff --git a/static/images/rc/migrate-data-active-passive-enable.png b/static/images/rc/migrate-data-active-passive-enable.png old mode 100755 new mode 100644 index 6736850de6c..0aac56ab76e Binary files a/static/images/rc/migrate-data-active-passive-enable.png and b/static/images/rc/migrate-data-active-passive-enable.png differ diff --git a/static/images/rc/migrate-data-add-active-passive.png b/static/images/rc/migrate-data-add-active-passive.png new file mode 100644 index 00000000000..f8eb65b012f Binary files /dev/null and b/static/images/rc/migrate-data-add-active-passive.png differ diff --git a/static/images/rc/migrate-data-specify-source-uri.png b/static/images/rc/migrate-data-specify-source-uri.png old mode 100755 new mode 100644 index 4d771c80a85..1095039431a Binary files a/static/images/rc/migrate-data-specify-source-uri.png and b/static/images/rc/migrate-data-specify-source-uri.png differ diff --git a/static/images/rc/migrate-data-tls-client-cert.png b/static/images/rc/migrate-data-tls-client-cert.png new file mode 100644 index 00000000000..a22a9066a75 Binary files /dev/null and b/static/images/rc/migrate-data-tls-client-cert.png differ diff --git a/static/images/rc/migrate-data-tls-server-cert.png b/static/images/rc/migrate-data-tls-server-cert.png new file mode 100644 index 00000000000..10490fb2617 Binary files /dev/null and b/static/images/rc/migrate-data-tls-server-cert.png differ