2017-12-12 23:24:37 +08:00
|
|
|
[[network.host]]
|
2020-10-19 22:02:22 +08:00
|
|
|
[discrete]
|
2021-04-29 09:30:32 +08:00
|
|
|
==== Network host setting
|
2017-12-12 23:24:37 +08:00
|
|
|
|
2021-02-01 21:06:20 +08:00
|
|
|
By default, {es} only binds to loopback addresses such as `127.0.0.1` and
|
|
|
|
`[::1]`. This is sufficient to run a cluster of one or more nodes on a single
|
|
|
|
server for development and testing, but a
|
|
|
|
<<high-availability-cluster-design,resilient production cluster>> must involve
|
|
|
|
nodes on other servers. There are many <<modules-network,network settings>> but
|
|
|
|
usually all you need to configure is `network.host`:
|
2017-12-12 23:24:37 +08:00
|
|
|
|
|
|
|
[source,yaml]
|
|
|
|
--------------------------------------------------
|
|
|
|
network.host: 192.168.1.10
|
|
|
|
--------------------------------------------------
|
|
|
|
|
2021-02-01 21:06:20 +08:00
|
|
|
IMPORTANT: When you provide a value for `network.host`, {es} assumes that you
|
|
|
|
are moving from development mode to production mode, and upgrades a number of
|
|
|
|
system startup checks from warnings to exceptions. See the differences between
|
|
|
|
<<dev-vs-prod,development and production modes>>.
|