github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-24 23:27:25 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Add note that write indices are not replicated (#82997)

Browse source 
* [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>
This commit is contained in:
Adam Locke 2022-01-28 13:24:53 -05:00 • committed by GitHub
parent e7ba03e0a6
commit 33b72f34e2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/reference/ccr/index.asciidoc
View file

@ -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 changes, you must update the leader index. Because they are read-only, follower
indices reject writes in all configurations. 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 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 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 to update `doc_1`, the request fails. To update `doc_1`, the client must