From 6c58123bd934611ec1c68b01c21d68797963a3c5 Mon Sep 17 00:00:00 2001 From: Kathryn May <44557882+kathancox@users.noreply.github.com> Date: Mon, 12 Aug 2024 16:17:08 -0400 Subject: [PATCH] Correct PCR known limitation duplicate and issue error (#18782) --- .../v23.2/known-limitations/physical-cluster-replication.md | 2 +- .../v24.1/known-limitations/cutover-stop-application.md | 2 +- .../v24.1/known-limitations/physical-cluster-replication.md | 1 - .../v24.2/known-limitations/cutover-stop-application.md | 2 +- .../v24.2/known-limitations/fast-cutback-latest-timestamp.md | 1 - .../v24.2/known-limitations/physical-cluster-replication.md | 1 - src/current/v24.2/cutover-replication.md | 4 ---- src/current/v24.2/known-limitations.md | 1 - src/current/v24.2/physical-cluster-replication-overview.md | 1 - 9 files changed, 3 insertions(+), 12 deletions(-) delete mode 100644 src/current/_includes/v24.2/known-limitations/fast-cutback-latest-timestamp.md diff --git a/src/current/_includes/v23.2/known-limitations/physical-cluster-replication.md b/src/current/_includes/v23.2/known-limitations/physical-cluster-replication.md index deff6e9b5ee..0a9fc624cf2 100644 --- a/src/current/_includes/v23.2/known-limitations/physical-cluster-replication.md +++ b/src/current/_includes/v23.2/known-limitations/physical-cluster-replication.md @@ -3,5 +3,5 @@ - The primary and standby cluster **cannot have different [region topology]({% link {{ page.version.version }}/topology-patterns.md %})**. For example, replicating a multi-region primary cluster to a single-region standby cluster is not supported. Mismatching regions between a multi-region primary and standby cluster is also not supported. - Cutting back to the primary cluster after a cutover is a manual process. Refer to [Cut back to the primary cluster]({% link {{ page.version.version }}/cutover-replication.md %}#cut-back-to-the-primary-cluster). In addition, after cutover, to continue using physical cluster replication, you must configure it again. - Before cutover to the standby, the standby cluster does not support running [backups]({% link {{ page.version.version }}/backup-and-restore-overview.md %}) or [changefeeds]({% link {{ page.version.version }}/change-data-capture-overview.md %}). -- After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. [Tracking GitHub issue](https://github.com/cockroachdb/cockroach/issues/117984) +- After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. - Large data imports, such as those produced by [`RESTORE`]({% link {{ page.version.version }}/restore.md %}) or [`IMPORT`]({% link {{ page.version.version }}/import.md %}), may dramatically increase [replication lag]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}#cutover-and-promotion-process). diff --git a/src/current/_includes/v24.1/known-limitations/cutover-stop-application.md b/src/current/_includes/v24.1/known-limitations/cutover-stop-application.md index 94ed342620e..1762f211c5a 100644 --- a/src/current/_includes/v24.1/known-limitations/cutover-stop-application.md +++ b/src/current/_includes/v24.1/known-limitations/cutover-stop-application.md @@ -1 +1 @@ -After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. [#117984](https://github.com/cockroachdb/cockroach/issues/117984) \ No newline at end of file +After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. \ No newline at end of file diff --git a/src/current/_includes/v24.1/known-limitations/physical-cluster-replication.md b/src/current/_includes/v24.1/known-limitations/physical-cluster-replication.md index fb951e9bbde..f914c7eced2 100644 --- a/src/current/_includes/v24.1/known-limitations/physical-cluster-replication.md +++ b/src/current/_includes/v24.1/known-limitations/physical-cluster-replication.md @@ -3,5 +3,4 @@ - The primary and standby cluster **cannot have different [region topology]({% link {{ page.version.version }}/topology-patterns.md %})**. For example, replicating a multi-region primary cluster to a single-region standby cluster is not supported. Mismatching regions between a multi-region primary and standby cluster is also not supported. - Cutting back to the primary cluster after a cutover is a manual process. Refer to [Cut back to the primary cluster]({% link {{ page.version.version }}/cutover-replication.md %}#cut-back-to-the-primary-cluster). In addition, after cutover, to continue using physical cluster replication, you must configure it again. - Before cutover to the standby, the standby cluster does not support running [backups]({% link {{ page.version.version }}/backup-and-restore-overview.md %}) or [changefeeds]({% link {{ page.version.version }}/change-data-capture-overview.md %}). -- After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. - Large data imports, such as those produced by [`RESTORE`]({% link {{ page.version.version }}/restore.md %}) or [`IMPORT INTO`]({% link {{ page.version.version }}/import-into.md %}), may dramatically increase [replication lag]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}#cutover-and-promotion-process). diff --git a/src/current/_includes/v24.2/known-limitations/cutover-stop-application.md b/src/current/_includes/v24.2/known-limitations/cutover-stop-application.md index 94ed342620e..1762f211c5a 100644 --- a/src/current/_includes/v24.2/known-limitations/cutover-stop-application.md +++ b/src/current/_includes/v24.2/known-limitations/cutover-stop-application.md @@ -1 +1 @@ -After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. [#117984](https://github.com/cockroachdb/cockroach/issues/117984) \ No newline at end of file +After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. \ No newline at end of file diff --git a/src/current/_includes/v24.2/known-limitations/fast-cutback-latest-timestamp.md b/src/current/_includes/v24.2/known-limitations/fast-cutback-latest-timestamp.md deleted file mode 100644 index 1a5b3b91a2c..00000000000 --- a/src/current/_includes/v24.2/known-limitations/fast-cutback-latest-timestamp.md +++ /dev/null @@ -1 +0,0 @@ -{% include {{ page.version.version }}/physical-replication/fast-cutback-latest-timestamp.md %} [#117984](https://github.com/cockroachdb/cockroach/issues/117984) \ No newline at end of file diff --git a/src/current/_includes/v24.2/known-limitations/physical-cluster-replication.md b/src/current/_includes/v24.2/known-limitations/physical-cluster-replication.md index fb951e9bbde..f914c7eced2 100644 --- a/src/current/_includes/v24.2/known-limitations/physical-cluster-replication.md +++ b/src/current/_includes/v24.2/known-limitations/physical-cluster-replication.md @@ -3,5 +3,4 @@ - The primary and standby cluster **cannot have different [region topology]({% link {{ page.version.version }}/topology-patterns.md %})**. For example, replicating a multi-region primary cluster to a single-region standby cluster is not supported. Mismatching regions between a multi-region primary and standby cluster is also not supported. - Cutting back to the primary cluster after a cutover is a manual process. Refer to [Cut back to the primary cluster]({% link {{ page.version.version }}/cutover-replication.md %}#cut-back-to-the-primary-cluster). In addition, after cutover, to continue using physical cluster replication, you must configure it again. - Before cutover to the standby, the standby cluster does not support running [backups]({% link {{ page.version.version }}/backup-and-restore-overview.md %}) or [changefeeds]({% link {{ page.version.version }}/change-data-capture-overview.md %}). -- After a cutover, there is no mechanism to stop applications from connecting to the original primary cluster. It is necessary to redirect application traffic manually, such as by using a network load balancer or adjusting DNS records. - Large data imports, such as those produced by [`RESTORE`]({% link {{ page.version.version }}/restore.md %}) or [`IMPORT INTO`]({% link {{ page.version.version }}/import-into.md %}), may dramatically increase [replication lag]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}#cutover-and-promotion-process). diff --git a/src/current/v24.2/cutover-replication.md b/src/current/v24.2/cutover-replication.md index b9e2e1c0d11..fddeca50e82 100644 --- a/src/current/v24.2/cutover-replication.md +++ b/src/current/v24.2/cutover-replication.md @@ -283,10 +283,6 @@ This section illustrates the steps to cut back to the original primary cluster f ALTER VIRTUAL CLUSTER {cluster_a} COMPLETE REPLICATION TO LATEST; ~~~ - {{site.data.alerts.callout_danger}} - {% include {{ page.version.version }}/physical-replication/fast-cutback-latest-timestamp.md %} - {{site.data.alerts.end}} - The `cutover_time` is the timestamp at which the replicated data is consistent. The cluster will revert any data above this timestamp: ~~~ diff --git a/src/current/v24.2/known-limitations.md b/src/current/v24.2/known-limitations.md index a9ab5b07f90..a68e36d7a4c 100644 --- a/src/current/v24.2/known-limitations.md +++ b/src/current/v24.2/known-limitations.md @@ -449,7 +449,6 @@ Accessing the DB Console for a secure cluster now requires login information (i. {% include {{ page.version.version }}/known-limitations/physical-cluster-replication.md %} - {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %} - {% include {{ page.version.version }}/known-limitations/cutover-stop-application.md %} -- {% include {{ page.version.version }}/known-limitations/fast-cutback-latest-timestamp.md %} #### `RESTORE` limitations diff --git a/src/current/v24.2/physical-cluster-replication-overview.md b/src/current/v24.2/physical-cluster-replication-overview.md index 13386570872..a821dbf366f 100644 --- a/src/current/v24.2/physical-cluster-replication-overview.md +++ b/src/current/v24.2/physical-cluster-replication-overview.md @@ -37,7 +37,6 @@ You can use PCR in a disaster recovery plan to: ## Known limitations {% include {{ page.version.version }}/known-limitations/physical-cluster-replication.md %} -- {% include {{ page.version.version }}/known-limitations/fast-cutback-latest-timestamp.md %} - {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %} - {% include {{ page.version.version }}/known-limitations/cutover-stop-application.md %}