-
Notifications
You must be signed in to change notification settings - Fork 468
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
Backport changes from #19002 #19138
Backport changes from #19002 #19138
Conversation
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
55ab610
to
dc7e870
Compare
@rmloveland There's a missing link breaking the build -- can you fix the link and redeploy so that I can check the previews? |
dc7e870
to
8c39381
Compare
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, one comment
@@ -248,7 +248,7 @@ The multiple active portals feature of the Postgres wire protocol (pgwire) is av | |||
|
|||
### Physical Cluster Replication | |||
|
|||
{% include_cached new-in.html version="v23.2" %}[Physical cluster replication]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) continuously sends all data at the byte level from a primary cluster to an independent standby cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. In a disaster recovery scenario, you can cut over from the unavailable primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time where all ingested data is consistent, and mark the standby as ready to accept application traffic. Physical cluster replication is in preview for CockroachDB Self-Hosted, and is an [enterprise-only]({% link {{ page.version.version }}/enterprise-licensing.md %}) feature. To share feedback and/or issues, contact [Support](https://support.cockroachlabs.com/hc). | |||
{% include_cached new-in.html version="v23.2" %}[Physical cluster replication]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) continuously sends all data at the byte level from a primary cluster to an independent standby cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster. In a disaster recovery scenario, you can cut over from the unavailable primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time where all ingested data is consistent, and mark the standby as ready to accept application traffic. Physical cluster replication is in preview for CockroachDB Self-Hosted. |
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.
Need to use the liquid var for "self-hosted" (and maybe append "clusters"). Sorry if I missed this in another PR.
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.
no you didn't miss anything, i think it was introduced by the merge skew because we already fixed this in #19083 and now it's back 👻
"Self-Hosted" came back even though it was killed in #19083
* Backport changes from #19008 (#19106) Addresses DOC-11674 Summary of changes: - Backport changes from #19008 to v23.1, v23.2, v24.1, and v24.2 * Backport changes from #19072 (#19109) * Backport changes from #19072 Addresses DOC-11674 Summary of changes: - Backport #19072 to v23.1, v23.2, v24.1, v24.2 * Backport changes from #19031 (#19108) Addresses DOC-11674 Summary of changes: - Backport #19031 to v23.1, v23.2, v24.1, v24.2 * Backport changes from #19001 (#19103) Addresses DOC-10665, DOC-11674 Summary of changes: - Backport changes from #19001; a few manual edits were required due to a few patches that didn't merge automagically * Backport changes from #19126 (#19133) Addresses DOC-11674, DOC-11692 * Merge origin/main into 20241029-DOC-10624-backports (#19140) * Merge origin/main back into core relicensing backport branch (#19142) * Backport changes from #19002 (#19138) * Backport changes from #19002 Addresses DOC-11674 * Backport telemetry docs from #19131 (#19145) Addresses DOC-11051 * Backport upgrade license info from #19125 (#19146) Addresses DOC-11693 * Fix broken link on upgrade page include --------- Co-authored-by: Rich Loveland <[email protected]>
Addresses DOC-11674
Backport changes from #19002