Skip to content

[DOC-12807]: Update Upgrade Matrix for Morpheus #3758

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

Open
wants to merge 1 commit into
base: release/8.0
Choose a base branch
from
Open

[DOC-12807]: Update Upgrade Matrix for Morpheus #3758

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
45 changes: 23 additions & 22 deletions modules/install/pages/upgrade.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
= Upgrade
:description: To upgrade a Couchbase-Server cluster means to upgrade the version of Couchbase Server that is running on every node.

:erlang-upgrade-note: The upgrade to Erlang support in Couchbase server 7.2.4 requires that you first upgrade Couchbase to version 7.1.0 or later before upgrading to version 7.6.x
:erlang-upgrade-note: The upgrade to Erlang support in Couchbase Server 8.0 requires that you first upgrade Couchbase to version 7.2 before upgrading to version 8.0

:xrefstyle: short

Expand All @@ -27,14 +27,14 @@ Before upgrading, consider the following version compatibility concerns.
// So long as upgrading from 6.x is supported, this notice will need to stay in some form in each new release.
=== Upgrading to Version 7.x With Earlier Versions of .NET SDK

When upgrading from Couchbase 6.5 or 6.6 to 7.0 or later determine if both of the following are true:
When upgrading from Couchbase 6.5 or 6.6 to 7.0 or later, determine if both of the following are true:

* You use a version of the .NET SDK prior to 3.2.9.
* Your cluster is in mixed mode networking where some nodes use IPv4 addressing and others use IPv6.
See xref:manage:manage-nodes/manage-address-families.adoc#changing-address-family-to-IPv6[Changing Address Family] for steps to determine if your cluster is running in this mode.

Using a version of the .NET SDK prior to 3.2.9 with mixed mode network addressing can cause issues with write operations.
Before upgrading, resolve the mixed mode networking issue.
Before upgrading, resolve the mixed-mode networking issue.


=== Upgrading from Pre-7.1 Versions of Couchbase Server
Expand All @@ -43,7 +43,7 @@ You cannot upgrade directly from a version of Couchbase Server earlier than 7.1
For example, you can directly upgrade from version 6.6 to version 7.2.3.
You cannot directly upgrade from version 6.6 to version 7.2.4.
A compatibility issue with the Erlang version used by these earlier server versions prevents a direct upgrade to later versions of the server.
To upgrade from server versions 6.5, 6.6, or 7.0 to version 7.6 or later, first upgrade to version between 7.1 and 7.2.3.
To upgrade from server versions 6.5, 6.6, or 7.0 to version 7.6 or later, first upgrade-to-version between 7.1 and 7.2.3.
Then upgrade to version 7.6 or later.

[#understanding-upgrade]
Expand All @@ -60,7 +60,7 @@ A review of the factors that determine the appropriateness of an upgrade-procedu
[#supported-upgrade-paths]
== Upgrade Paths

An upgrade _path_ declares that the upgrade of one version of Couchbase Server to another is _supported_.
An upgrade _path_ declares that the upgrade of one Couchbase Server version to another is _supported_.
The tables in the following subsections list upgrade paths for Enterprise Edition and for Community Edition, respectively.
Each instance of the{nbsp}`->`{nbsp}sign declares support for the upgrade of the server-version on the left of the sign to the server-version on the right.

Expand All @@ -77,19 +77,17 @@ TIP: As far as is possible, you should aim to keep your cluster up to date with
|===
| Starting Version | Path to Current Version

| 5.0.x

| 5.0.x and 5.1.x -> 6.6 -> 7.2.3 -> 7.6.x{blank}xref:#erlang-7-2-4-footnote1[^+[1]+^]

| 5.5x
| 5.x

| 5.5.0+ -> 6.6 -> 7.2.3 -> 7.6.x{blank}xref:#erlang-7-2-4-footnote1[^+[1]+^]
| Any 5.0.x / 5.1.x / 5.5.x → 6.6 → 7.2.3 → 8.0

| 6.x
| 6.0 -> 6.6 -> 7.2.3 -> 7.6.x{blank}xref:#erlang-7-2-4-footnote1[^+[1]+^]
| Any 6.0.x / 6.5.x → 6.6 → 7.2.3 → 8.0

| 7.x
| 7.0 -> 7.1 -> 7.6.x{blank}xref:#erlang-7-2-4-footnote1[^+[1]+^]
| Any 7.0.x / 7.1.x → 7.2.3→ 8.0{empty}xref:#erlang-7-2-4-footnote1[^+[1]+^]

Any 7.2.x / 7.6.x → 8.0

|===

Expand All @@ -104,13 +102,13 @@ TIP: As far as is possible, you should aim to keep your cluster up to date with
| Starting Version | Path to Current Version

| 5.x
| 5.x -> 6.6 -> 7.2.3 -> 7.6.x{blank}xref:erlang-7-2-4-footnote2[^+[1]+^]
| 5.x → 6.6 → 7.2.3 → 7.6.x[{empty}xref:erlang-7-2-4-footnote2[^+[1]+^]

| 6.x
| 6.0 -> 6.6 -> 7.2.3 -> 7.6.x{blank}xref:erlang-7-2-4-footnote2[^+[1]+^]
| 6.0 → 6.6 → 7.2.3 → 7.6.x{empty}xref:erlang-7-2-4-footnote2[^+[1]+^]

| 7.x
| 7.0 -> 7.1 -> 7.6.x{blank}xref:erlang-7-2-4-footnote2[^+[1]+^]
| 7.0 → 7.1 → 7.6.x{empty}xref:erlang-7-2-4-footnote2[^+[1]+^]



Expand Down Expand Up @@ -196,7 +194,7 @@ and finally, from *7.2.3* to *7.6.x*.

If you’re currently operating a Couchbase Server cluster on Community Edition, you can upgrade it to Enterprise Edition by way of a xref:upgrade-strategies.adoc#online-upgrade[rolling online upgrade].
This involves switching out the Community Edition nodes with fresh, net-new Enterprise Edition nodes.
Both swap rebalance and remove and reblance methods are supported.
Both swap rebalance and remove and rebalance methods are supported.
Delta Recovery is not supported since the new nodes must be fresh Enterprise Edition installations without any pre-existing Community Edition data remaining on them.

NOTE: Rolling upgrades from CE to EE are not supported if there are index service nodes running in the cluster.
Expand All @@ -217,11 +215,12 @@ include::partial$diagrams.adoc[tag="upgrade-diagram"]
.Additional Notes about Upgrading from Community to Enterprise
[sidebar]
****
* Couchbase Server clusters _must_ be run either entirely on Enterprise Edition nodes, or entirely on Community Edition nodes. +
* Couchbase Server clusters _must_ be run either entirely on Enterprise Edition nodes or entirely on Community Edition nodes. +
Once you've upgraded one node to Enterprise Edition, you must upgrade all the other nodes before the cluster is considered as being in a steady, supportable state.
* CE does not support index service rebalancing.
So, when the cluster is running with one or more CE nodes, then the indexes hosted on nodes being removed may be lost. +
Users can create equivalent indexes (same index with different name) on different nodes, to avoid loss of index functionality.
Users can create equivalent indexes (the same index with a different name) on different nodes
to avoid loss of index functionality.
* If a rolling online upgrade to Enterprise Edition isn't possible in your environment, contact Couchbase for assistance.
****

Expand All @@ -232,8 +231,10 @@ If you're interested in upgrading to Couchbase Server Enterprise Edition, check
====


See xref:install:upgrade-procedure-selection.adoc[Upgrade Procedure-Selection], for a list of procedures that can be used when upgrading from Community Edition to Enterprise.
Note, however, that _Graceful Failover_ for Data Service nodes, with _Delta Recovery_, is _not_ supported for such upgrades: instead, _removal_, _addition_, and _swap rebalance_ should be used; for all nodes.
See xref:install:upgrade-procedure-selection.adoc[Upgrade Procedure-Selection] for a list of procedures
that can be used when upgrading from Community Edition to Enterprise.
Note, however, that _Graceful Failover_ for Data Service nodes, with _Delta Recovery_,
is _not_ supported for such upgrades: instead, _removal_, _addition_, and _swap rebalance_ should be used; for all nodes.

[#node-naming-and-upgrade]
== Node-Naming and Upgrade
Expand All @@ -246,7 +247,7 @@ For information, see xref:learn:security/certificates.adoc#node-certificate-vali
== Downgrade

Once an upgrade of a Couchbase-Server cluster has started,
_downgrade_ to the earlier version of Couchbase Server can be performed,
_a downgrade_ to the earlier version of Couchbase Server can be performed,
as long as one node continues to run the earlier version.
To downgrade an existing node, you must first remove the existing Linux package installer, then install an earlier version.
However, once all nodes are running the later version, downgrade can no longer be performed: therefore,
Expand Down