From 2a387b1d3a199d04436bd06d51bfd0723ae2450a Mon Sep 17 00:00:00 2001 From: Alexander Scheel Date: Mon, 28 Nov 2022 14:39:41 -0500 Subject: [PATCH] Clarify that cluster_id differs between PR Primary/Secondary clusters (#18130) Per conversation on Slack with Nick. Co-authored-by: Nick Cabatoff Signed-off-by: Alexander Scheel Signed-off-by: Alexander Scheel Co-authored-by: Nick Cabatoff --- .../api-docs/system/replication/replication-performance.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/api-docs/system/replication/replication-performance.mdx b/website/content/api-docs/system/replication/replication-performance.mdx index 60d9d9ddf..564f87c0c 100644 --- a/website/content/api-docs/system/replication/replication-performance.mdx +++ b/website/content/api-docs/system/replication/replication-performance.mdx @@ -62,7 +62,7 @@ secondary, it will look something like: ```json { "data": { - "cluster_id": "d4095d41-3aee-8791-c421-9bc7f88f7c3e", + "cluster_id": "06dcf957-6630-44ae-bdd9-117d5f4d70d7", "known_primary_cluster_addrs": ["https://127.0.0.1:8201"], "last_remote_wal": 87, "merkle_root": "c31e40f6ff02f32c37b70e6a4d58732ac812abf0",