From 14ef513f2c6906f407c6be7dfeea784c42b725bd Mon Sep 17 00:00:00 2001 From: Leaf-Lin <39002973+Leaf-Lin@users.noreply.github.com> Date: Tue, 18 Oct 2022 07:05:29 +1100 Subject: [PATCH] [DOCS] Add CCR limitation (#87348) * Add CCR limitation closes https://github.com/elastic/elasticsearch/issues/86121 * Add restored index auto follow pattern restriction https://github.com/elastic/elasticsearch/issues/87055 * Moving content to existing CCR page + several changes * Remove sections to consolidate limitation information * Delete separate file * Remove restored indices from list of things that aren't replicated Co-authored-by: Adam Locke Co-authored-by: Elastic Machine --- docs/reference/ccr/index.asciidoc | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc index 6357630e87d1..e1b6e98ea5d8 100644 --- a/docs/reference/ccr/index.asciidoc +++ b/docs/reference/ccr/index.asciidoc @@ -313,6 +313,32 @@ and use {ccr}: * <> * <> +[discrete] +[[ccr-limitations]] +=== {ccr-cap} limitations +{ccr-cap} is designed to replicate user-generated indices only, and doesn't +currently replicate any of the following: + +* <> +* {ml-docs}/machine-learning-intro.html[Machine learning jobs] +* <> +* <> and +<> polices +* {ref}/mapping-roles.html[User permissions and role mappings] +* <> +* <> +* <> + +If you want to replicate any of this data, you must replicate it to a remote +cluster manually. + +NOTE: Data for <> indices is stored in +the snapshot repository. {ccr-cap} won't replicate these indices completely, even +though they're either partially or fully-cached on the {es} nodes. To achieve +searchable snapshots in a remote cluster, configure snapshot repositories on +the remote cluster and use the same {ilm} policy from the local cluster to move +data into the cold or frozen tiers on the remote cluster. + include::getting-started.asciidoc[] include::managing.asciidoc[] include::auto-follow.asciidoc[]