Conversation
|
|
||
| When you're upgrading between major or minor versions of Couchbase Server, you can downgrade at any time before you finalize your upgrade. | ||
| Finalizing an upgrade means that all nodes in the cluster are running the new version of Couchbase Server. | ||
|
|
There was a problem hiding this comment.
Here, can we add a sentence like below with a link to the "Preventing Finalization" section?
(For a tip on preventing finalization, see Preventing Finalization.)
I realize that the section Preventing Finalization is just a few sentences down, but with people skimming and only reading couple of sentences of paragraphs, repetition may be helpful here.
| . Installing the earlier version of Couchbase Server. | ||
| . Migrating your data to the new cluster. | ||
|
|
||
| Because finalization increas__es the difficulty in rolling back an upgrade, it's vital to test the new version with your applications before you finalize it. |
There was a problem hiding this comment.
typo -- "Because finalization incres__es" -- should be "Because finalization increases"
| The only concern about a maintenance version downgrade is if you enabled any new features using Developer Preview Mode. | ||
| See xref:developer-preview:preview-mode.adoc[] for more information about Developer Preview Mode and the features it enables. | ||
| If you have enabled Developer Preview Mode, contact Couchbase Customer Support for assistance before attempting to downgrade your cluster. |
There was a problem hiding this comment.
My comments apply to lines 357-359:
I don't think that you can downgrade after you've put a cluster into Developer Preview Mode, and since you can't return a cluster to production mode after you've switched to Developer Preview Mode, it's not really even a concern -- especially since there are already warnings in the documentation about the developer preview mode not being a GA offering.
The issue is if they are using hidden features that engineering has made available to select customers via diag/eval commands -- this would have been done through Support. So, not sure how to phrase that in a public documentation.
So, something like:
If you are using a special maintenance version or a diagnostic feature acquired through Support or other Couchbase programs, contact Couchbase Support for assistance before attempting to downgrade your cluster. If you've enabled new features using the Developer Preview Mode, you will not be able to downgrade.
2 participants
These changes address DOC-14003 which asks for some clarifications to the downgrade section of the Upgrading page.
The changes were adding in two places in the Upgrade page: