Update discovery-ec2.asciidoc (#28925)
* Be more clear about the need to defining tags in EC2 to be able to filter ES instances.
This commit is contained in:
parent
100ef2cc0e
commit
ed2b5e80eb
|
@ -185,9 +185,9 @@ Management Console. It should look similar to this.
|
||||||
===== Filtering by Tags
|
===== Filtering by Tags
|
||||||
|
|
||||||
The ec2 discovery can also filter machines to include in the cluster based on tags (and not just groups). The settings
|
The ec2 discovery can also filter machines to include in the cluster based on tags (and not just groups). The settings
|
||||||
to use include the `discovery.ec2.tag.` prefix. For example, setting `discovery.ec2.tag.stage` to `dev` will only
|
to use include the `discovery.ec2.tag.` prefix. For example, if you defined a tag `stage` in EC2 and set it to `dev`,
|
||||||
filter instances with a tag key set to `stage`, and a value of `dev`. Several tags set will require all of those tags
|
setting `discovery.ec2.tag.stage` to `dev` will only filter instances with a tag key set to `stage`, and a value
|
||||||
to be set for the instance to be included.
|
of `dev`. Adding multiple `discovery.ec2.tag` settings will require all of those tags to be set for the instance to be included.
|
||||||
|
|
||||||
One practical use for tag filtering is when an ec2 cluster contains many nodes that are not running Elasticsearch. In
|
One practical use for tag filtering is when an ec2 cluster contains many nodes that are not running Elasticsearch. In
|
||||||
this case (particularly with high `discovery.zen.ping_timeout` values) there is a risk that a new node's discovery phase
|
this case (particularly with high `discovery.zen.ping_timeout` values) there is a risk that a new node's discovery phase
|
||||||
|
|
Loading…
Reference in New Issue