Skip to content
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.

Sign up for GitHub

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

Jira DOC-929: Add additional details about the upgrade policy to the upgrade doc. #1599

Merged
merged 3 commits into from
Oct 19, 2021
Merged

Jira DOC-929: Add additional details about the upgrade policy to the upgrade doc. #1599

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c6aa481
Initial draft
lanceleonard Oct 13, 2021
e196ad6
Promoting section.
lanceleonard Oct 13, 2021
32f4bef
Incoporating editorial feedback.
lanceleonard Oct 14, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 33 additions & 10 deletions content/rs/installing-upgrading/upgrading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,39 @@ To upgrade successfully, both of the following must be true:

If you do not meet these minimums, you must first update the nodes and databases accordingly.

## Redis upgrade policy

In version 6.2.4, Redis Enterprise Software introduced the Redis database compatibility upgrade policy (`redis_upgrade_policy`). This policy controls the default value for the Redis database compatibility used to create new and update existing databases.
lanceleonard marked this conversation as resolved.
Show resolved Hide resolved

As of v6.2.4, this policy defaults to `major`, which limits Redis database compatibility to the most recent major release (v6.0, as of this writing.). To create databases using the most recent release of Redis, use `rladmin` to set the policy to `latest`.

``` shell
tune cluster redis_upgrade_policy latest
```

The policy supports the following values:

- When set to `major`, the policy allows databases to be created or updated to versions of Redis compatible with open source Redis major releases. This allows for longer upgrade cycles by supporting Redis versions across multiple Redis Enterprise Software releases.

This is the default value for Redis Enterprise Software.

- When set to `latest`, the policy creates new databases and upgrades existing ones to be compatible with the latest (most recent) version of open source Redis, which was the default behavior of earlier versions of Redis Enterprise Software. This is no longer the default behavior.
lanceleonard marked this conversation as resolved.
Show resolved Hide resolved

Setting the upgrade policy to `latest` ensures that the most recent Redis features are available to new databases and ones that are upgraded. It also requires more frequent upgrades, as open source Redis is updated more frequently than Redis Enterprise Software.

To demonstrate: The Redis Enterprise Software 6.2.4 package included compatibility with the most recent major Redis release (v6.0 at the time) and the latest (most recent) update to Redis (v6.2.3 at the time).

By default, compatibility with v6.0 was installed with the upgrade.

To change this to use the latest release available, use `rladmin` to set the upgrade policy and the default Redis version:

``` shell
tune cluster redis_upgrade_policy latest
tune cluster default_redis_version 6.2
```

The default policy value supports a more conservative approach to upgrades. Changing the policy to `latest` provides access to the more recent feature changes; however, it requires more frequent upgrades to stay current.
lanceleonard marked this conversation as resolved.
Show resolved Hide resolved

## Upgrade a cluster

### Upgrade prerequisites
Expand Down Expand Up @@ -108,16 +141,6 @@ Before upgrading a database:

- When persistence is enabled without replication, the database is unavailable during restart because the data is restored from the persistence file. AOF persistence restoration is slower than snapshot restoration.

### Redis database upgrade policy

In version 6.2.4, Redis Enterprise Software introduced the Redis database compatibility upgrade policy (`redis_upgrade_policy`). This policy controls the default value for the Redis database compatibility used to create new and update existing databases. To learn more, see [`rladmin upgrade`]({{< relref "/rs/references/rladmin.md#upgrade" >}}).

As of v6.2.4, this policy defaults to `major`, which limits Redis database compatibility to the most recent major release (v6.0, as of this writing.). To create databases using the most recent release of Redis, use `rladmin` to set the policy to `latest`.

``` shell
tune cluster redis_upgrade_policy latest
```

### Database upgrade process

To upgrade a database:
Expand Down
2 changes: 1 addition & 1 deletion content/rs/release-notes/rs-6-2-4-august-2021.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Keep the following in mind:

- [In v6.0.20]({{<relref "/rs/release-notes/rs-6-0-20-april-2021.md">}}), Redis Enterprise Software replaced Nginx with envoy to improve internal security and communication. As of v6.2.4, Nginx is no longer provided with Redis Enterprise Software.

### Database upgrade defaults
### Database upgrade default changes

The default behavior of the `upgrade db` command has changed. It is now controlled by a new cluster policy (`redis_upgrade_policy`), which defines the policy for creating new databases and upgrading existing databases. The policy supports the following values:

Expand Down