From c83477c5045d2363071f7331bb0537d04d8acb68 Mon Sep 17 00:00:00 2001 From: Pius Date: Thu, 26 Sep 2019 12:37:02 -0700 Subject: [PATCH] Added a direct reference to remote cluster page This has come up multiple times from the field in the past. Some users have trouble finding version compatibility information for CCR clusters. This information is well documented at https://www.elastic.co/guide/en/elasticsearch/reference/7.3/modules-remote-clusters.html. We are actually implicitly linking this already via the link to the Kibana documentation in this statement: "For more information about managing cross-cluster replication in Kibana, see Working with remote clusters." (Kibana docs then link to the remote clusters page). CCS documentation (https://www.elastic.co/guide/en/elasticsearch/reference/7.3/modules-cross-cluster-search.html) has a nice explicit link to remote clusters at the beginning of the page. This is just an attempt to adopt the same note at the beginning of the CCR documentation for consistency. Hopefully, this will make it easier for end users to find the nice compatibility information upfront. --- docs/reference/ccr/overview.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/ccr/overview.asciidoc b/docs/reference/ccr/overview.asciidoc index 8f25cb1da4735..16f7c7d48df10 100644 --- a/docs/reference/ccr/overview.asciidoc +++ b/docs/reference/ccr/overview.asciidoc @@ -17,6 +17,7 @@ Replication is pull-based. This means that replication is driven by the follower index. This simplifies state management on the leader index and means that {ccr} does not interfere with indexing on the leader index. +IMPORTANT: {ccr-cap} requires <>. ==== Configuring replication @@ -213,4 +214,4 @@ following process starts again. You can terminate replication with the {ref}/ccr-post-unfollow.html[unfollow API]. This API converts a follower index -to a regular (non-follower) index. \ No newline at end of file +to a regular (non-follower) index.