[DOCS] add details on version compatibility and remote gateway selection #40056
Conversation
This file contains 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 commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
javanna
added
>docs
|
Pinging @elastic/es-distributed |
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 14, 2019
lcawl
reviewed
Mar 15, 2019
| is referenced by a name and a list of seed nodes. When a remote cluster is | ||
| registered, its cluster state is retrieved from one of the seed nodes and up | ||
| to three _gateway nodes_ are selected to be connected to as part of remote | ||
| cluster requests. All the communication required between different clusters |
There was a problem hiding this comment.
three gateway nodes are selected to be connected to as part of remote cluster requests
It is unclear at this point in the page whether those three gateway nodes are used permanently or just for a particular request or whether the selection can change over time...?
There was a problem hiding this comment.
They are used for all CCR and CCS requests from then on. The selection may change if one or more of those nodes are shut down, in that case they will get replaced.
There was a problem hiding this comment.
Thanks, I think we should add that piece of info here.
lcawl
reviewed
Mar 15, 2019
lcawl
reviewed
Mar 15, 2019
| @@ -211,4 +253,5 @@ PUT _cluster/settings | |||
|
|
|||
| You can use the <<cluster-remote-info, remote cluster info API>> to retrieve | |||
| information about the configured remote clusters, as well as the remote nodes | |||
| that the node is connected to. | |||
| that the node is connected to. This is particularly useful to verify which | |||
There was a problem hiding this comment.
as well as the remote nodes that the node is connected to.
The API reference information (https://www.elastic.co/guide/en/elasticsearch/reference/master/cluster-remote-info.html) implies that "connected" is true/false. Is that correct or does it list the gateway nodes?
There was a problem hiding this comment.
very good point. we do return a list of nodes but it's the list of seed nodes apparently rather than the selected gateway nodes, I need to adapt this then. Thanks for noticing!
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
Co-Authored-By: javanna <javanna@users.noreply.github.com>
javanna
commented
Mar 15, 2019
| version to the cluster on the lower version, since they support communicating with both ends. For instance, a 7.0 | ||
| cluster can communicate with 6.6 or earlier nodes as long as at least one 6.7 | ||
| _gateway node_ is present in their cluster. Beware that only features | ||
| supported by the lower version can be used in that case. |
There was a problem hiding this comment.
I will remove this note, I got feedback that it may be problematic for CCR and I also find it a bit confusing.
javanna
added a commit
to javanna/elasticsearch
that referenced
this pull request
Mar 19, 2019
…ion (elastic#40056) This commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
javanna
added a commit
to javanna/elasticsearch
that referenced
this pull request
Mar 19, 2019
…ion (elastic#40056) This commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
javanna
added a commit
to javanna/elasticsearch
that referenced
this pull request
Mar 19, 2019
…ion (elastic#40056) This commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
This was referenced Mar 19, 2019
javanna
added a commit
that referenced
this pull request
Mar 19, 2019
…ion (#40056) This commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
javanna
added a commit
that referenced
this pull request
Mar 19, 2019
…ion (#40056) This commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
javanna
added a commit
that referenced
this pull request
Mar 19, 2019
…ion (#40056) This commit clarifies how the gateway selection works when configuring remote clusters for CCR or CCS. Specifically, it clarifies compatibility between different versions which is a very common question.
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 commit clarifies how the gateway selection works when configuring
remote clusters for CCR or CCS. Specifically, it clarifies compatibility
between different versions which is a very common question.