From 15fd69393acb9e24d7226a16a2d13e4f6074df9b Mon Sep 17 00:00:00 2001 From: Adam Locke Date: Fri, 28 Jan 2022 14:22:00 -0500 Subject: [PATCH] [DOCS] Add note that write indices are not replicated (#82997) (#83279) * [DOCS] Add note that write indices are not replicated * Clarify note about is_write_index * Clarify leader aliases with is_write_index Co-authored-by: Henning Andersen <33268011+henningandersen@users.noreply.github.com> Co-authored-by: Henning Andersen <33268011+henningandersen@users.noreply.github.com> Co-authored-by: Henning Andersen <33268011+henningandersen@users.noreply.github.com> --- docs/reference/ccr/index.asciidoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc index b46f6171f1bce..c39b875446598 100644 --- a/docs/reference/ccr/index.asciidoc +++ b/docs/reference/ccr/index.asciidoc @@ -195,6 +195,11 @@ 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 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 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