github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-25 07:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Document supported scenarios for CCS (#58120)

Browse source 
Documents the supported scenarios for CCS.

Co-authored-by: Adam Locke <adam.locke@elastic.co>
This commit is contained in:
Nik Everett 2020-07-20 10:03:08 -04:00 • committed by GitHub
parent 6bfde550f9
commit f87b31f973
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/reference/modules/cross-cluster-search.asciidoc
View file

@ -372,3 +372,21 @@ image:images/ccs/ccs-dont-min-roundtrip-shard-results.svg[]
final results in the {ccs} response. final results in the {ccs} response.
+ +
image:images/ccs/ccs-min-roundtrip-client-response.svg[] image:images/ccs/ccs-min-roundtrip-client-response.svg[]
[discrete]
[[ccs-supported-configurations]]
=== Supported configurations
Generally, <<gateway-nodes-selection, cross cluster search>> 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
<<rolling-upgrades, upgraded>> 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.