From 610161baf7ba27e56e628307c4ffde63ef27844f Mon Sep 17 00:00:00 2001 From: Woody Walton <12531513+woodywalton@users.noreply.github.com> Date: Tue, 29 Jan 2019 10:54:43 -0500 Subject: [PATCH] Clarify the remote clusters seeds setting Clarify the required value for the `seeds` setting, specifically that it requires the `transport.tcp.port` (as opposed to the `http.port`) of the remote cluster. --- docs/reference/modules/remote-clusters.asciidoc | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/reference/modules/remote-clusters.asciidoc b/docs/reference/modules/remote-clusters.asciidoc index 81d882f5f0eb6..b44e769ec3bf2 100644 --- a/docs/reference/modules/remote-clusters.asciidoc +++ b/docs/reference/modules/remote-clusters.asciidoc @@ -41,21 +41,23 @@ driven specifically from those nodes. Remote clusters set via the in the cluster. The `elasticsearch.yml` config file for a node that connects to remote clusters -needs to list the remote clusters that should be connected to, for instance: +needs to list the remote clusters that should be connected to. The format for each +`seeds` entry is `remote_host`:`transport.tcp.port`, for instance: [source,yaml] -------------------------------- cluster: remote: cluster_one: <1> - seeds: 127.0.0.1:9300 - cluster_two: <1> seeds: 127.0.0.1:9301 + cluster_two: <1> + seeds: 127.0.0.1:9302 -------------------------------- <1> `cluster_one` and `cluster_two` are arbitrary _cluster aliases_ representing the connection to each cluster. These names are subsequently used to distinguish -between local and remote indices. +between local and remote indices. In this example, `cluster_one` is using port `9301` +for transport, and `cluster_two` is using port `9302`. The equivalent example using the <> to add remote clusters to all nodes in the cluster would look like the