From b32a30abe36e1d4655ce06953c0691d974627e52 Mon Sep 17 00:00:00 2001 From: Peter Dyson Date: Thu, 24 May 2018 13:31:18 +1000 Subject: [PATCH] [Docs] Add reindex.remote.whitelist example (#30828) --- docs/reference/docs/reindex.asciidoc | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/reference/docs/reindex.asciidoc b/docs/reference/docs/reindex.asciidoc index e8283abfc2ef0..f8273642e8434 100644 --- a/docs/reference/docs/reindex.asciidoc +++ b/docs/reference/docs/reindex.asciidoc @@ -432,7 +432,15 @@ Remote hosts have to be explicitly whitelisted in elasticsearch.yaml using the `reindex.remote.whitelist` property. It can be set to a comma delimited list of allowed remote `host` and `port` combinations (e.g. `otherhost:9200, another:9200, 127.0.10.*:9200, localhost:*`). Scheme is -ignored by the whitelist - only host and port are used. +ignored by the whitelist - only host and port are used, for example: + + +[source,yaml] +-------------------------------------------------- +reindex.remote.whitelist: "otherhost:9200, another:9200, 127.0.10.*:9200, localhost:*" +-------------------------------------------------- + +The whitelist must be configured on any nodes that will coordinate the reindex. This feature should work with remote clusters of any version of Elasticsearch you are likely to find. This should allow you to upgrade from any version of