Skip to content

[DOCS] Document CCR compatibility requirements #49776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jrodewig merged 1 commit into from
Dec 2, 2019
Merged

[DOCS] Document CCR compatibility requirements #49776

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/reference/ccr/overview.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,18 @@ 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 <<modules-remote-clusters, remote clusters>>.
In {ccr}, the cluster performing this pull is known as the _local cluster_. The
cluster being replicated is known as the _remote cluster_.

==== Prerequisites

* {ccr-cap} requires <<modules-remote-clusters, remote clusters>>.

* The {es} version of the local cluster must be **the same as or newer** than
the remote cluster. If newer, the versions must also be compatible as outlined
in the following matrix.

include::../modules/remote-clusters.asciidoc[tag=remote-cluster-compatibility-matrix]

==== Configuring replication

Expand Down
2 changes: 2 additions & 0 deletions docs/reference/modules/remote-clusters.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@ node, while 6.7 can only communicate with 7.0. Version compatibility is
symmetric, meaning that if 6.7 can communicate with 7.0, 7.0 can also
communicate with 6.7. The matrix below summarizes compatibility as described above.

// tag::remote-cluster-compatibility-matrix[]
[cols="^,^,^,^,^,^,^,^"]
|====
| Compatibility | 5.0->5.5 | 5.6 | 6.0->6.6 | 6.7 | 6.8 | 7.0 | 7.1->7.x
Expand All @@ -54,6 +55,7 @@ communicate with 6.7. The matrix below summarizes compatibility as described abo
| 7.0 | No | No | No | Yes | Yes | Yes | Yes
| 7.1->7.x | No | No | No | No | Yes | Yes | Yes
|====
// end::remote-cluster-compatibility-matrix[]

- *role*: Dedicated master nodes never get selected.
- *attributes*: You can tag which nodes should be selected
Expand Down