Skip to content

document PCR read from standby limitation in all affected versions #23255

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.

Sign up for GitHub

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

Merged
taroface merged 4 commits into from
May 13, 2026
+22 −2
Merged

document PCR read from standby limitation in all affected versions #23255

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ed2419e
document PCR read from standby limitation in all affected versions
taroface May 5, 2026
1ba6aa1
remove PCR read from standby limitation for v26.2, v26.1, v25.4
taroface May 13, 2026
6c73ab4
remove GitHub issue link from PCR known limitation
taroface May 13, 2026
7ea677e
Merge branch 'main' into pcr-known-limitation
taroface May 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions src/current/_includes/releases/v26.2/v26.2.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -503,8 +503,6 @@ This section describes newly identified limitations in CockroachDB v26.2.
ALTER VIRTUAL CLUSTER {reader_vc} START SERVICE SHARED;
~~~

[#169078](https://github.com/cockroachdb/cockroach/issues/169078)

#### Hint injections

- [Statement hints]({% link v26.2/cost-based-optimizer.md %}#statement-hints) do not apply to statements within views. The workaround for `REWRITE INLINE HINTS` is to modify the inline hints directly in the body by replacing the view. There is no workaround for `SET VARIABLE` hints. [#166782](https://github.com/cockroachdb/cockroach/issues/166782)
Expand Down
11 changes: 11 additions & 0 deletions src/current/_includes/v24.3/known-limitations/physical-cluster-replication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,15 @@
- CockroachDB {{ site.data.products.core }} clusters on v23.2 or later. The primary cluster can be a [new]({% link {{ page.version.version }}/set-up-physical-cluster-replication.md %}#step-1-create-the-primary-cluster) or [existing]({% link {{ page.version.version }}/set-up-physical-cluster-replication.md %}#set-up-pcr-from-an-existing-cluster) cluster. The standby cluster must be a [new cluster started with the `--virtualized-empty` flag]({% link {{ page.version.version }}/set-up-physical-cluster-replication.md %}#step-2-create-the-standby-cluster).
- [CockroachDB {{ site.data.products.advanced }} clusters]({% link cockroachcloud/physical-cluster-replication.md %}) on v24.3 or later.
- In CockroachDB {{ site.data.products.core }}, the primary and standby clusters must have the same [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) in order to respect data placement configurations.
- When using the [read from standby]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}#start-up-sequence-with-read-on-standby) feature, startup of the reader virtual cluster can occasionally stall after the initial scan or after an upgrade, preventing SQL connections to the reader virtual cluster. To mitigate this issue, restart the virtual cluster service on the standby cluster's system virtual cluster:

{% include_cached copy-clipboard.html %}
~~~ sql
ALTER VIRTUAL CLUSTER {reader_vc} STOP SERVICE;
~~~

{% include_cached copy-clipboard.html %}
~~~ sql
ALTER VIRTUAL CLUSTER {reader_vc} START SERVICE SHARED;
~~~

11 changes: 11 additions & 0 deletions src/current/_includes/v25.2/known-limitations/physical-cluster-replication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,14 @@
- CockroachDB {{ site.data.products.core }} clusters on v23.2 or later. The primary cluster can be a [new]({% link {{ page.version.version }}/set-up-physical-cluster-replication.md %}#step-1-create-the-primary-cluster) or [existing]({% link {{ page.version.version }}/set-up-physical-cluster-replication.md %}#set-up-pcr-from-an-existing-cluster) cluster. The standby cluster must be a [new cluster started with the `--virtualized-empty` flag]({% link {{ page.version.version }}/set-up-physical-cluster-replication.md %}#step-2-create-the-standby-cluster).
- [CockroachDB {{ site.data.products.advanced }} clusters]({% link cockroachcloud/physical-cluster-replication.md %}) on v24.3 or later.
- In CockroachDB {{ site.data.products.core }}, the primary and standby clusters must have the same [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) in order to respect data placement configurations.
- When using the [read from standby]({% link {{ page.version.version }}/physical-cluster-replication-technical-overview.md %}#start-up-sequence-with-read-on-standby) feature, startup of the reader virtual cluster can occasionally stall after the initial scan or after an upgrade, preventing SQL connections to the reader virtual cluster. To mitigate this issue, restart the virtual cluster service on the standby cluster's system virtual cluster:

{% include_cached copy-clipboard.html %}
~~~ sql
ALTER VIRTUAL CLUSTER {reader_vc} STOP SERVICE;
~~~

{% include_cached copy-clipboard.html %}
~~~ sql
ALTER VIRTUAL CLUSTER {reader_vc} START SERVICE SHARED;
~~~
Loading