From ede1fe8ae303ec46e1d55a16181ad4068ffcc385 Mon Sep 17 00:00:00 2001 From: Adam Locke Date: Mon, 24 Jan 2022 17:02:25 -0500 Subject: [PATCH 1/3] [DOCS] Add note that write indices are not replicated --- docs/reference/ccr/index.asciidoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc index b46f6171f1bce..da3dbd076baad 100644 --- a/docs/reference/ccr/index.asciidoc +++ b/docs/reference/ccr/index.asciidoc @@ -195,6 +195,10 @@ You can't manually modify a follower index's mappings or aliases. To make changes, you must update the leader index. Because they are read-only, follower indices reject writes in all configurations. +NOTE: Although changes to aliases on the leader index are replicated to follower +indices, write indices are ignored. Follower indices can't accept direct writes, +so any indices where `is_write_index` is `true` are not replicated. + For example, you index a document named `doc_1` in Datacenter A, which replicates to Datacenter B. If a client connects to Datacenter B and attempts to update `doc_1`, the request fails. To update `doc_1`, the client must From 9b5260f943435367546c41852b58cd8349e94d4d Mon Sep 17 00:00:00 2001 From: Adam Locke Date: Fri, 28 Jan 2022 11:14:57 -0500 Subject: [PATCH 2/3] Clarify note about is_write_index --- docs/reference/ccr/index.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc index da3dbd076baad..bfdfcd886ef1d 100644 --- a/docs/reference/ccr/index.asciidoc +++ b/docs/reference/ccr/index.asciidoc @@ -197,7 +197,8 @@ indices reject writes in all configurations. NOTE: Although changes to aliases on the leader index are replicated to follower indices, write indices are ignored. Follower indices can't accept direct writes, -so any indices where `is_write_index` is `true` are not replicated. +so if any follower indices have `is_write_index` set to `true`, that value is +forced to `false`. For example, you index a document named `doc_1` in Datacenter A, which replicates to Datacenter B. If a client connects to Datacenter B and attempts From d59bda24f3359c7ff17904632ad76d3f3613bdaa Mon Sep 17 00:00:00 2001 From: Adam Locke Date: Fri, 28 Jan 2022 12:28:15 -0500 Subject: [PATCH 3/3] Clarify leader aliases with is_write_index Co-authored-by: Henning Andersen <33268011+henningandersen@users.noreply.github.com> --- docs/reference/ccr/index.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc index bfdfcd886ef1d..c39b875446598 100644 --- a/docs/reference/ccr/index.asciidoc +++ b/docs/reference/ccr/index.asciidoc @@ -197,7 +197,7 @@ indices reject writes in all configurations. NOTE: Although changes to aliases on the leader index are replicated to follower indices, write indices are ignored. Follower indices can't accept direct writes, -so if any follower indices have `is_write_index` set to `true`, that value is +so if any leader aliases have `is_write_index` set to `true`, that value is forced to `false`. For example, you index a document named `doc_1` in Datacenter A, which