From fe1014110854316e6d73ca5ba88668521c0b8051 Mon Sep 17 00:00:00 2001 From: Nik Everett Date: Mon, 20 Jul 2020 10:41:53 -0400 Subject: [PATCH] Document supported scenarios for CCS (#58120) (#59886) Documents the supported scenarios for CCS. Co-authored-by: Adam Locke --- .../modules/cross-cluster-search.asciidoc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/reference/modules/cross-cluster-search.asciidoc b/docs/reference/modules/cross-cluster-search.asciidoc index 064deda8228..217806c0e33 100644 --- a/docs/reference/modules/cross-cluster-search.asciidoc +++ b/docs/reference/modules/cross-cluster-search.asciidoc @@ -376,3 +376,21 @@ image:images/ccs/ccs-dont-min-roundtrip-shard-results.svg[] final results in the {ccs} response. + image:images/ccs/ccs-min-roundtrip-client-response.svg[] + +[discrete] +[[ccs-supported-configurations]] +=== Supported configurations + +Generally, <> can search remote +clusters that are one major version ahead or behind the coordinating node's +version. Cross cluster search can also search remote clusters that are being +<> so long as both the "upgrade from" and +"upgrade to" version are compatible with the gateway node. + +For example, a coordinating node running {es} 5.6 can search a remote cluster +running {es} 6.8, but that cluster can not be upgraded to 7.1. In this case +you should first upgrade the coordinating node to 7.1 and then upgrade remote +cluster. + +WARNING: Running multiple versions of {es} in the same cluster beyond the +duration of an upgrade is not supported.