-
Notifications
You must be signed in to change notification settings - Fork 190
RC: Version managment phase B #1374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
a7bde0e
a0503ec
f5c89f2
5967ea4
1811476
cd2ad45
d181aaf
2a4ac7c
e771b9c
58fb57d
ca3d8a6
5949427
f4b25eb
af6d113
ac2bf91
f2eedc9
29d4e44
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -93,10 +93,9 @@ The **Setup** tab specifies general settings for your Redis deployment. | |
|
||
{{<image filename="images/rc/subscription-new-flexible-tabs-setup.png" width="75%" alt="The Setup tab of the new Pro Database process." >}} | ||
|
||
There are three sections on this tab: | ||
There are two sections on this tab: | ||
|
||
- [General settings](#general-settings) include the cloud provider details and specific configuration options. | ||
- [Version](#version) lets you choose the Redis version of your databases. | ||
- [Advanced options](#advanced-options) define settings for high availability and security. Configurable settings vary according to cloud provider. | ||
|
||
#### General settings {#general-settings} | ||
|
@@ -113,12 +112,6 @@ In the **General settings** of the **Setup** tab, you need to: | |
This guide is for single region database deployment. If you want to create a multi-region Active-Active database, see [Create an Active-Active database]({{< relref "/operate/rc/databases/create-database/create-active-active-database" >}}) for specific steps and configuration options exclusive to Active-Active. | ||
{{< /note >}} | ||
|
||
#### Version {#version} | ||
|
||
{{<image filename="images/rc/subscription-new-flexible-version-section.png" width="75%" alt="Version selection between Redis 6.2, 7.2, and 7.4." >}} | ||
|
||
The **Version** section lets you choose the Redis version of your databases. Choose **Redis 7.4** if you want to use the latest stable version of Redis. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. to prevent doc update on evry new version, let's just write that we recommand to use the latest |
||
|
||
#### Advanced options {#advanced-options} | ||
|
||
{{<image filename="images/rc/subscription-new-flexible-setup-advanced.png" width="75%" alt="The Advanced settings of the Setup tab." >}} | ||
|
@@ -158,6 +151,7 @@ By default, you're shown basic settings, which include: | |
| Database setting | Description | | ||
|:---------|:-----------| | ||
| **Name** | A custom name for your database (_required_) | | ||
| **Version** | The Redis version for your database. We recommend you choose the latest available version. | | ||
| **Dataset size (GB)** | The amount of data for your dataset. Specify small sizes as decimals of 1.0 GB; example: `0.1` GB (minimum). We calculate the total memory limit for you based on the other settings you choose for your database. <br/> Databases with Search and query have specific sizing requirements, see [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | ||
| **High Availability** | Indicates whether a replica copy of the database is maintained in case the primary database becomes unavailable. (Warning: Doubles memory consumption). See [High Availability]({{< relref "/operate/rc/databases/configuration/high-availability" >}}). | | ||
| **Throughput** | Identifies maximum throughput for the database, which is specified in terms of operations per second (**Ops/sec**). See [Throughput]({{< relref "/operate/rc/databases/configuration/sizing#throughput" >}}) for more information. <br/> Databases with Search and query have specific throughput requirements. See [Search and query sizing]({{< relref "/operate/rc/databases/configuration/advanced-capabilities#search-and-query-sizing" >}}) for more information. | | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @cmilesb let's also write a note somewhere on the page that it is recommended to perform the DB upgrade during off-peak hours. Maybe in addition to the note about reviewing the release notes before upgrading. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,82 @@ | ||
--- | ||
Title: Upgrade Redis database version | ||
alwaysopen: false | ||
categories: | ||
- docs | ||
- operate | ||
- rc | ||
description: Describes when you can upgrade your database to the latest available version for each plan type. | ||
linkTitle: Upgrade database version | ||
weight: 37 | ||
--- | ||
|
||
Database version upgrade options depend on your plan type. | ||
|
||
## Redis Cloud Essentials | ||
|
||
All new Redis Cloud Essentials databases are on the latest available version of Redis. Redis will notify Redis Cloud Essentials users when a new database version is available. | ||
|
||
## Redis Cloud Pro | ||
|
||
Redis Cloud Pro databases that are not on the latest available version of Redis can be upgraded to a later version at any time. | ||
|
||
{{< note >}} | ||
Please keep in mind the following before upgrading your database version: | ||
|
||
- We recommend that you [back up your data]({{< relref "/operate/rc/databases/back-up-data" >}}) before upgrading to make it easier to [manually revert the upgrade](#manually-revert-upgrade) if needed. | ||
|
||
- Review the breaking changes for the new database version before upgrading: | ||
- [Redis 7.2]({{< relref "/operate/rc/changelog/2023/june-2023#redis-72-breaking-changes" >}}) | ||
- [Redis 7.4]({{< relref "/operate/rc/changelog/july-2024#redis-74-breaking-changes" >}}) | ||
|
||
- You must upgrade the target database in an [Active-Passive]({{< relref "/operate/rc/databases/migrate-databases#sync-using-active-passive" >}}) setup before you upgrade the source database to prevent compatibility issues. | ||
{{< /note >}} | ||
|
||
### Upgrade Redis Cloud Pro database | ||
|
||
{{< note >}} | ||
Upgrading a single Redis Cloud Pro database is available for selected accounts and will be rolled out gradually to other accounts in the future. If you don't see **Version upgrade** in the **More actions** menu for your database and your database version is not the latest available version, you can request to upgrade all of the databases in your subscription from the [subscription page]({{< relref "/operate/rc/subscriptions/view-pro-subscription" >}}). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @NoamSternRedis Do you want to keep this note? You mentioned wanting to remove it from the embed (and thus from the view-pro-subscription page), but do we want to mention the rollout here and in the changelog? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should remove this note |
||
{{< /note >}} | ||
|
||
To upgrade a Redis Cloud Pro database: | ||
|
||
1. Choose your database from the **Databases** list to open your database page. Select **More actions > Version upgrade**. | ||
|
||
{{<image filename="images/rc/databases-more-actions-menu.png" alt="The More Actions menu on the Database page." width=40% >}} | ||
|
||
You can also select **More actions > Version upgrade** from the database list. | ||
|
||
1. Select the target version from the **Select version** list. | ||
|
||
{{<image filename="images/rc/database-version-upgrade.png" alt="The Redis version upgrade screen." width=80% >}} | ||
|
||
If your database has not been backed up before, we recommend that you back up your database. Select **Go to backup** to go to the [backup settings]({{< relref "/operate/rc/databases/back-up-data" >}}). | ||
|
||
1. Select **Upgrade** to start the upgrade. | ||
|
||
{{<image filename="images/rc/button-upgrade.png" alt="The upgrade button." width=100px >}} | ||
|
||
The database will start upgrading to the selected version immediately. The upgrade may take a few minutes. | ||
|
||
You can continue to use the Redis Cloud console for other tasks during the upgrade. | ||
|
||
### Manually revert upgrade | ||
|
||
Automatically reverting to a previous Redis version is not supported on Redis Cloud. | ||
|
||
If you [backed up your database]({{< relref "/operate/rc/databases/back-up-data" >}}) before you upgraded your version, you can: | ||
|
||
1. [Delete your database]({{< relref "/operate/rc/databases/delete-database" >}}) without deleting your subscription. | ||
1. [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) in your subscription with the following settings: | ||
- **Port number**: Use the same port number as the old database. | ||
- **Version**: Select the original version of Redis. | ||
1. [Import the backup files]({{< relref "/operate/rc/databases/import-data" >}}) into the new database. | ||
|
||
This allows you to connect to the database on the previous version without changing your connection details in your application. | ||
|
||
If you did not back up your database before upgrading: | ||
cmilesb marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
1. [Back up your database]({{< relref "/operate/rc/databases/back-up-data" >}}). | ||
1. [Create a new database]({{< relref "/operate/rc/databases/create-database/create-pro-database-existing" >}}) in your subscription and select the original version of Redis. | ||
1. [Import the backup files]({{< relref "/operate/rc/databases/import-data" >}}) into the new database. | ||
1. Change connection details in your application from the old database to the new database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to prevent doc update on evry new version, let's just write that we recommand to use the latest