Skip to content

[DOC-1047] xCluster DR version and automatic mode updates #29187

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
merged 6 commits into from
Nov 4, 2025
Merged

[DOC-1047] xCluster DR version and automatic mode updates #29187

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
095c2e8
version and mode updates
aishwarya24 Oct 30, 2025
5a685ff
change from review
aishwarya24 Oct 31, 2025
88a2390
minor miss
aishwarya24 Oct 31, 2025
2b18292
Merge branch 'master' into update-xc
aishwarya24 Nov 3, 2025
6209d68
change from review
aishwarya24 Nov 3, 2025
671397f
added warning
aishwarya24 Nov 3, 2025
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: 1 addition & 1 deletion .../stable/yugabyte-platform/back-up-restore-universes/disaster-recovery/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ Automatic mode is recommended for all new DR configurations. When possible, you

Automatic mode is used for any xCluster DR configuration when the following pre-requisites are met at setup time:

- Both DR primary and replica are running YugabyteDB {{<release "2025.1.0">}} or later.
- Both DR primary and replica are running YugabyteDB {{<release "2025.1.1">}} or later.
- Automatic mode is enabled. While in {{<tags/feature/ea idea="2089">}}, the feature is not enabled by default. To enable it, set the **Automatic mode for xCluster** Global runtime configuration option (config key `yb.xcluster.db_scoped.automatic_ddl.creationEnabled`) to true. Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/). Note that only a Super Admin user can modify Global runtime configuration settings.
- Semi-automatic mode is enabled. Semi-automatic mode is enabled by default, and set using the **DB scoped xCluster replication creation** Global Runtime Configuration option (config key `yb.xcluster.db_scoped.creationEnabled`).

Expand Down
16 changes: 12 additions & 4 deletions ...latform/back-up-restore-universes/disaster-recovery/disaster-recovery-tables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,14 @@ For each DDL statement:

After both steps are complete, the YugabyteDB Anywhere UI should reflect any added/removed tables in the Tables listing for this DR configuration.

In addition, keep in mind the following:

- If you are using Colocated tables, you CREATE TABLE on DR primary, then CREATE TABLE on DR replica making sure that you force the Colocation ID to be identical to that on DR primary.
- If you try to make a DDL change on DR primary and it fails, you must also make the same attempt on DR replica and get the same failure.
- TRUNCATE TABLE is not supported. To truncate a table, pause replication, truncate the table on both primary and standby, and resume replication.

Use the following guidance when managing tables and indexes in universes with DR configured.

{{% /tab %}}

{{% tab header="Manual mode" lang="manual-mode" %}}
Expand All @@ -51,10 +59,6 @@ You should perform these actions in a specific order, depending on whether perfo
| ALTER TABLE<br>ADD CONSTRAINT UNIQUE | Execute on Primary | Execute on Replica | [Reconcile configuration](#reconcile-configuration) |
| ALTER TABLE<br>DROP CONSTRAINT<br>(unique constraints only) | Execute on Replica | Execute on Primary | [Reconcile configuration](#reconcile-configuration) |

{{% /tab %}}

{{</tabpane >}}

In addition, keep in mind the following:

- If you are using Colocated tables, you CREATE TABLE on DR primary, then CREATE TABLE on DR replica making sure that you force the Colocation ID to be identical to that on DR primary.
Expand All @@ -63,6 +67,10 @@ In addition, keep in mind the following:

Use the following guidance when managing tables and indexes in universes with DR configured.

{{% /tab %}}

{{</tabpane >}}

Copy link
Contributor

@hari90 hari90 Oct 31, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

None of the below (Tables, Indexes, .....) apply to Automatic or Semi-Automatic mode. This entire doc needs to be updated

Copy link
Contributor

@hari90 hari90 Oct 31, 2025

Choose a reason for hiding this comment

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

Lets remove it all, and also remove manual mode.
cc @shahrooz1997

Copy link
Contributor

@shahrooz1997 shahrooz1997 Oct 31, 2025

Choose a reason for hiding this comment

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

We cannot remove the manual doc. there are customers using that mode and we also need them for bidirectional setup and management.

Copy link
Contributor

@hari90 hari90 Oct 31, 2025

Choose a reason for hiding this comment

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

BiDirectional should NOT be in the DR section.
Manual is deprecated. Anyone on 2025.2 should be on semi-automatic. Lets make sure YBA also does not allow manual mode DR in 2025.2.0

Copy link
Contributor

@shahrooz1997 shahrooz1997 Oct 31, 2025

Choose a reason for hiding this comment

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

my bad, this is DR only and we don't have bidirectional for DR

## Tables

Note: If you are performing application upgrades involving both adding and dropping tables, perform the upgrade in two parts: first add tables, then drop tables.
Expand Down