@@ -68,14 +68,14 @@ startup.
6868
6969To enable file-based discovery, configure the `file` hosts provider as follows:
7070
71- ```
71+ [source,txt]
72+ ----------------------------------------------------------------
7273discovery.zen.hosts_provider: file
73- ```
74+ ----------------------------------------------------------------
7475
75- Then create a file at `$ES_PATH_CONF/unicast_hosts.txt` in
76- <<discovery-file-format,the format described below>>. Any time a change is made
77- to the `unicast_hosts.txt` file the new changes will be picked up by
78- Elasticsearch and the new hosts list will be used.
76+ Then create a file at `$ES_PATH_CONF/unicast_hosts.txt` in the format described
77+ below. Any time a change is made to the `unicast_hosts.txt` file the new
78+ changes will be picked up by Elasticsearch and the new hosts list will be used.
7979
8080Note that the file-based discovery plugin augments the unicast hosts list in
8181`elasticsearch.yml`: if there are valid unicast host entries in
@@ -86,10 +86,6 @@ The `discovery.zen.ping.unicast.resolve_timeout` setting also applies to DNS
8686lookups for nodes specified by address via file-based discovery. This is
8787specified as a <<time-units, time unit>> and defaults to 5s.
8888
89- [[discovery-file-format]]
90- [float]
91- ====== unicast_hosts.txt file format
92-
9389The format of the file is to specify one node entry per line. Each node entry
9490consists of the host (host name or IP address) and an optional transport port
9591number. If the port number is specified, is must come immediately after the
0 commit comments