Skip to content

Commit 2c64a9a

Browse files
nik9000Adam Locke
andauthored
Document supported scenarios for CCS (backport of #58120) (#59894)
Documents the supported scenarios for CCS. Co-authored-by: Adam Locke <[email protected]>
1 parent 7aee0d0 commit 2c64a9a

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/reference/modules/cross-cluster-search.asciidoc

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -376,3 +376,21 @@ image:images/ccs/ccs-dont-min-roundtrip-shard-results.svg[]
376376
final results in the {ccs} response.
377377
+
378378
image:images/ccs/ccs-min-roundtrip-client-response.svg[]
379+
380+
[discrete]
381+
[[ccs-supported-configurations]]
382+
=== Supported configurations
383+
384+
Generally, <<gateway-nodes-selection, cross cluster search>> can search remote
385+
clusters that are one major version ahead or behind the coordinating node's
386+
version. Cross cluster search can also search remote clusters that are being
387+
<<rolling-upgrades, upgraded>> so long as both the "upgrade from" and
388+
"upgrade to" version are compatible with the gateway node.
389+
390+
For example, a coordinating node running {es} 5.6 can search a remote cluster
391+
running {es} 6.8, but that cluster can not be upgraded to 7.1. In this case
392+
you should first upgrade the coordinating node to 7.1 and then upgrade remote
393+
cluster.
394+
395+
WARNING: Running multiple versions of {es} in the same cluster beyond the
396+
duration of an upgrade is not supported.

0 commit comments

Comments
 (0)