Doc: Added a direct reference to remote cluster page #47185
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
ppf2
added
:Distributed Indexing/CCR
|
Pinging @elastic/es-docs |
|
Pinging @elastic/es-distributed |
jrodewig
approved these changes
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
jrodewig
pushed a commit
that referenced
this pull request
Sep 26, 2019
|
@ppf2 This doesn't answer the compatibility question though, CCR has a stricter compatibility requirement than remote clusters do. The local cluster (the one that is pulling from the remote cluster) must be of a compatible version equal to or newer than the version of the remote cluster. The reason is the same as for allocation of replicas: the local cluster must be able to understand the Lucene segment files that are sent to it, as well as any index settings, mappings, etc. |
|
Thanks @jasontedor and @ppf2. I created #47218 so we can track this request and change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This has come up multiple times from the field in the past. Some users have trouble finding version compatibility information for CCR clusters, even though 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 the above already via the link to the Kibana documentation as part of this statement: "For more information about managing cross-cluster replication in Kibana, see Working with remote clusters." (the Kibana docs then link back 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.