honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-24 17:09:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Update discovery plugins example configuration with discovery.zen.hosts_provider (#21390)

Browse Source 
This new setting was added with deguicing unicast hosts providers, but
the docs were not updated.
This commit is contained in:
Ryan Ernst 2016-11-07 13:33:08 -08:00 committed by GitHub
parent 1f0c6cd137
commit edb9d8fc03
4 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/plugins/discovery-azure-classic.asciidoc
View File

@ -56,7 +56,7 @@ cloud:
type: pkcs12
discovery:
type: azure
zen.hosts_provider: azure
----
[IMPORTANT]

2
docs/plugins/discovery-ec2.asciidoc
View File

@ -139,7 +139,7 @@ environments). Here is a simple sample configuration:
[source,yaml]
----
discovery:
type: ec2
zen.hosts_provider: ec2
----
You must also set `cloud.aws.region` if you are not using default AWS region. See <<discovery-ec2-usage-region>> for details.

14
docs/plugins/discovery-file.asciidoc
View File

@ -39,11 +39,15 @@ The node must be stopped before removing the plugin.
The file-based discovery plugin provides the ability to specify the
unicast hosts list through a simple `unicast_hosts.txt` file that can
be dynamically updated at any time. The discovery type for this plugin
is still the default `zen` plugin, so no changes are required to the
`elasticsearch.yml` config file. This plugin simply provides a facility
to supply the unicast hosts list for zen discovery through an external
file that can be updated at any time by a side process.
be dynamically updated at any time. To enable, add the following in `elasticsearch.yml`:
[source,yaml]
----
discovery.zen.hosts_provider: file
----
This plugin simply provides a facility to supply the unicast hosts list for
zen discovery through an external file that can be updated at any time by a side process.
For example, this gives a convenient mechanism for an Elasticsearch instance
that is run in docker containers to be dynamically supplied a list of IP

2
docs/plugins/discovery-gce.asciidoc
View File

@ -46,7 +46,7 @@ cloud:
project_id: <your-google-project-id>
zone: <your-zone>
discovery:
type: gce
zen.hosts_provider: gce
--------------------------------------------------
The following gce settings (prefixed with `cloud.gce`) are supported: