@@ -68,14 +68,14 @@ startup.
68
68
69
69
To enable file-based discovery, configure the `file` hosts provider as follows:
70
70
71
- ```
71
+ [source,txt]
72
+ ----------------------------------------------------------------
72
73
discovery.zen.hosts_provider: file
73
- ```
74
+ ----------------------------------------------------------------
74
75
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.
79
79
80
80
Note that the file-based discovery plugin augments the unicast hosts list in
81
81
`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
86
86
lookups for nodes specified by address via file-based discovery. This is
87
87
specified as a <<time-units, time unit>> and defaults to 5s.
88
88
89
- [[discovery-file-format]]
90
- [float]
91
- ====== unicast_hosts.txt file format
92
-
93
89
The format of the file is to specify one node entry per line. Each node entry
94
90
consists of the host (host name or IP address) and an optional transport port
95
91
number. If the port number is specified, is must come immediately after the
0 commit comments