Fixed discovery.zen.ping.unicast.hosts example. <host>:<port> didn't work without code formating.
This commit is contained in:
parent
504dded158
commit
492fdc3750
1 changed files with 1 additions and 1 deletions
|
|
@ -68,7 +68,7 @@ When not utilizing multicast, the following should be set to ensure a successful
|
||||||
|
|
||||||
* ```es_config['http.port']``` - the http port for the node
|
* ```es_config['http.port']``` - the http port for the node
|
||||||
* ```es_config['transport.tcp.port']``` - the transport port for the node
|
* ```es_config['transport.tcp.port']``` - the transport port for the node
|
||||||
* ```es_config['discovery.zen.ping.unicast.hosts']``` - the unicast discovery list, in the comma separated format "<host>:<port>,<host>:<port>" (typically the clusters dedicated masters)
|
* ```es_config['discovery.zen.ping.unicast.hosts']``` - the unicast discovery list, in the comma separated format ```"<host>:<port>,<host>:<port>"``` (typically the clusters dedicated masters)
|
||||||
* ```es_config['network.host']``` - sets both network.bind_host and network.publish_host to the same host value. The network.bind_host setting allows to control the host different network components will bind on.
|
* ```es_config['network.host']``` - sets both network.bind_host and network.publish_host to the same host value. The network.bind_host setting allows to control the host different network components will bind on.
|
||||||
|
|
||||||
The network.publish_host setting allows to control the host the node will publish itself within the cluster so other nodes will be able to connect to it.
|
The network.publish_host setting allows to control the host the node will publish itself within the cluster so other nodes will be able to connect to it.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue