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.

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

Update the upgrades section for PCR for more detailed guidance #18809

Merged
merged 3 commits into from
Aug 13, 2024

Conversation

kathancox
Copy link
Contributor

Fixes DOC-10835

This PR adjusts the upgrade section for PCR to provide an ordered list of the steps between the system vc and vc as well as the primary + standby.

Copy link

netlify bot commented Aug 9, 2024

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit a3104f7
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-interactivetutorials-docs/deploys/66bb85f3a5b001000866a5ca

Copy link

netlify bot commented Aug 9, 2024

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit a3104f7
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-api-docs/deploys/66bb85f3c94db20008cc2174

Copy link

netlify bot commented Aug 9, 2024

Netlify Preview

Name Link
🔨 Latest commit a3104f7
🔍 Latest deploy log https://app.netlify.com/sites/cockroachdb-docs/deploys/66bb85f34449990008f4d484
😎 Deploy Preview https://deploy-preview-18809--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@kathancox
Copy link
Contributor Author

Hi @alicia-l2, are these the kind of changes you had in mind for this section?

@alicia-l2
Copy link

small thing, could we also get rid of the cluster size on the pages as well? when we discuss what scale we support PCR at


When physical cluster replication is enabled, we recommend following this procedure on the standby cluster first, before upgrading the primary cluster. It is preferable to avoid a situation in which the application virtual cluster, which is being replicated, is a version higher than what the standby cluster can serve if you were to cut over.
The standby cluster must be at the same version as, or one version ahead of, the primary's virtual cluster at the time of [cutover]({% link {{ page.version.version }}/cutover-replication.md %}).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be more emphatic about this -- you absolutely should not start or do steady state or cutover in PCR when the standby cluster is at a lower version than the primary. I think we'll add guardrails for this soon but as of right now we should really call this out in the docs (maybe like a warning sign box)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added this to a warning box in this section and in the ## Start clusters section

@@ -122,11 +122,15 @@ Statement | Action

### Cluster versions and upgrades

The standby cluster must be at the same version as, or one version ahead of, the primary's application virtual cluster at the time of cutover.
When PCR is enabled, we recommend upgrading with the following procedure. This upgrades the standby cluster before the primary cluster. It is preferable to avoid a situation where the virtual cluster, which is being replicated, is a version higher than what the standby cluster can serve if you were to cut over. Within the primary and standby CockroachDB clusters, the system virtual cluster must be at a cluster version greater than or equal to the virtual cluster:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should remove "recommend upgrading" and just say "upgrade"

@@ -122,11 +122,15 @@ Statement | Action

### Cluster versions and upgrades

The standby cluster must be at the same version as, or one version ahead of, the primary's application virtual cluster at the time of cutover.
When PCR is enabled, we recommend upgrading with the following procedure. This upgrades the standby cluster before the primary cluster. It is preferable to avoid a situation where the virtual cluster, which is being replicated, is a version higher than what the standby cluster can serve if you were to cut over. Within the primary and standby CockroachDB clusters, the system virtual cluster must be at a cluster version greater than or equal to the virtual cluster:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"It is preferable to avoid a situation where the virtual cluster, which is being replicated, is a version higher than what the standby cluster can serve if you were to cut over." not sure if we need this sentence

@@ -122,11 +122,15 @@ Statement | Action

### Cluster versions and upgrades

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ordering wise, i wonder if this makes sense to be at the bottom of the "get started" section

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved the section!

Copy link

@alicia-l2 alicia-l2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm thank you!

Copy link
Contributor

@rmloveland rmloveland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kathancox kathancox merged commit dd6f32a into main Aug 13, 2024
6 checks passed
@kathancox kathancox deleted the pcr-upgrade-details branch August 13, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants