Skip to content
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

Backport of update website docs for new update-primary mode into release/1.13.x #20429

Merged
merged 1 commit into from
Apr 28, 2023
+14 −0
Merged

Backport of update website docs for new update-primary mode into release/1.13.x #20429

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 7 additions & 0 deletions website/content/api-docs/system/replication/replication-dr.mdx
View file
Original file line number Diff line number Diff line change
@@ -471,6 +471,13 @@ docs](#generate-disaster-recovery-operation-token) for more information.
PEM-format files that the secondary can use when unwrapping the token from the
primary. If this and ca_file are not given, defaults to system CA roots.

- `update_primary_addrs` `array: []` – List of cluster addresses for potential
primary clusters. These addresses will be pinged in sequence, and if any of them
respond successfully, these will be recorded as the new primary addresses. This is
a lighter weight version of specifying a token and should result in less disruption
of replication. Note that it's invalid to specify this and `token` in the same API call.
They are mutually exclusive.

### Sample Payload

```json
7 changes: 7 additions & 0 deletions website/content/api-docs/system/replication/replication-performance.mdx
View file
Original file line number Diff line number Diff line change
@@ -562,6 +562,13 @@ secondary activation token. This does not wipe all data in the cluster.
PEM-format files that the secondary can use when unwrapping the token from the
primary. If this and ca_file are not given, defaults to system CA roots.

- `update_primary_addrs` `array: []` – List of cluster addresses for potential
primary clusters. These addresses will be pinged in sequence, and if any of them
respond successfully, these will be recorded as the new primary addresses. This is
a lighter weight version of specifying a token and should result in less disruption
of replication. Note that it's invalid to specify this and `token` in the same API call.
They are mutually exclusive.

### Sample Payload

```json