-
Notifications
You must be signed in to change notification settings - Fork 476
Clarified usage of read from standby #22036
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?
Conversation
Added clarifying info to show that read from standby should only be used for ad hoc analytics queries
Files changed: |
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| {{ site.data.alerts.callout_info }} | ||
| Write operations are not permitted on the standby cluster. | ||
| Only use the read from standby feature for ad-hoc analytics queries. To run read replicas, or to leverage `AS OF SYSTEM TIME` for read-only workloads, use [follower reads]({% link {{ page.version.version }}/follower-reads.md %}) instead. Write operations are not permitted on the standby cluster. |
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.
I think a better way to frame this would be: PCR's primary use case is disaster recovery. The read from standby feature allows you to better utilize the hardware required for PCR's standby cluster. If you are simply looking for a workload isolation solution without a DR requirement, we recommend deploying a single cluster and leveraging follower reads.
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.
@msbutler thanks for the feedback- just rewrote the note to be more from this perspective
Adjusted to focus on broader use case based on tech review
| ## Use the read from standby feature | ||
|
|
||
| {{ site.data.alerts.callout_info }} | ||
| The read from standby feature allows you to utilize your standby cluster to increase efficiency when you are already using PCR. However, PCR's primary use case is disaster recovery, not workload isolation. If you need a workload isolation solution but do not need disaster recovery, deploy a single cluster and use [follower reads]({% link {{ page.version.version }}/follower-reads.md %}) instead. |
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.
utilize your standby cluster to increase efficiency
I think "increase efficiency" is unclear. what about "... feature allows you to increase PCR standby cluster hardware utilization during replication."
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.
Sure, that makes sense- I'll change that
Changed wording based on tech review
…oachdb/docs into 20260105-doc-15575-rfs-ad-hoc-only
rmloveland
left a comment
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.
LGTM
Fixes: DOC-15575
Added clarifying info to show that read from standby should only be used for ad hoc analytics queries