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

[DOCS] Clarify when changes are replicated in CCR (#83863)

Browse source 
Removes a table, which some users found confusing (refer to https://github.com/elastic/sdh-elasticsearch/issues/4009). Clarifies language around when changes are replicated from the leader index to the follower index.
This commit is contained in:
Adam Locke 2022-02-11 16:07:38 -05:00 • committed by GitHub
parent b2e196fe91
commit 950c231e04
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -216,19 +216,11 @@ To manage how operations are replicated from the leader index, you can
configure settings when
<<ccr-getting-started-follower-index,creating the follower index>>.
The follower index automatically retrieves some updates applied to the leader
index, while other updates are retrieved as needed:
[cols="3"]
|===
h| Update type h| Automatic h| As needed
| Alias | {yes-icon} | {no-icon}
| Mapping | {no-icon} | {yes-icon}
| Settings | {no-icon} | {yes-icon}
|===
For example, changing the number of replicas on the leader index is not
replicated by the follower index, so that setting might not be retrieved.
Changes in the index mapping on the leader index are replicated to the
follower index as soon as possible. This behavior is true for index
settings as well, except for some settings that are local to the leader
index. For example, changing the number of replicas on the leader index is
not replicated by the follower index, so that setting might not be retrieved.
If you apply a non-dynamic settings change to the leader index that is
needed by the follower index, the follower index closes itself, applies the