OpenSearch/docs/reference/modules/network.asciidoc

182 lines
6.0 KiB
Plaintext
Raw Normal View History

[[modules-network]]
2015-12-10 05:24:25 -05:00
== Network Settings
2015-12-10 05:24:25 -05:00
Elasticsearch binds to localhost only by default. This is sufficient for you
to run a local development server (or even a development cluster, if you start
multiple nodes on the same machine), but you will need to configure some
<<common-network-settings,basic network settings>> in order to run a real
production cluster across multiple servers.
2015-12-10 05:24:25 -05:00
[WARNING]
.Be careful with the network configuration!
=============================
Never expose an unprotected node to the public internet.
=============================
2015-12-10 05:24:25 -05:00
[float]
[[common-network-settings]]
=== Commonly Used Network Settings
`network.host`::
The node will bind to this hostname or IP address and _publish_ (advertise) this
host to other nodes in the cluster. Accepts an IP address, hostname, a
<<network-interface-values,special value>>, or an array of any combination of
these. Note that any values containing a `:` (e.g., an IPv6 address or
containing one of the <<network-interface-values,special value>>) must be quoted
because `:` is a special character in YAML.
2015-12-10 05:24:25 -05:00
+
Defaults to `_local_`.
`discovery.seed_hosts`::
2015-12-10 05:24:25 -05:00
In order to join a cluster, a node needs to know the hostname or IP address of
2016-02-09 05:07:32 -05:00
at least some of the other nodes in the cluster. This setting provides the
initial list of addresses this node will try to contact. Accepts IP addresses
or hostnames. If a hostname lookup resolves to multiple IP addresses then each
IP address will be used for discovery.
https://en.wikipedia.org/wiki/Round-robin_DNS[Round robin DNS] -- returning a
different IP from a list on each lookup -- can be used for discovery; non-
existent IP addresses will throw exceptions and cause another DNS lookup on the
next round of pinging (subject to JVM DNS caching). + Defaults to
`["127.0.0.1", "[::1]"]`.
2015-12-10 05:24:25 -05:00
`http.port`::
2015-12-10 05:24:25 -05:00
Port to bind to for incoming HTTP requests. Accepts a single value or a range.
If a range is specified, the node will bind to the first available port in the
range.
+
Defaults to `9200-9300`.
`transport.port`::
2015-12-10 05:24:25 -05:00
Port to bind for communication between nodes. Accepts a single value or a
range. If a range is specified, the node will bind to the first available port
in the range.
+
Defaults to `9300-9400`.
2015-12-09 14:10:21 -05:00
[float]
2015-12-10 05:24:25 -05:00
[[network-interface-values]]
2015-12-09 14:10:21 -05:00
=== Special values for `network.host`
2015-12-10 05:24:25 -05:00
The following special values may be passed to `network.host`:
[horizontal]
`_[networkInterface]_`::
2015-12-10 05:24:25 -05:00
Addresses of a network interface, for example `_en0_`.
Fix network binding for ipv4/ipv6 When elasticsearch is configured by interface (or default: loopback interfaces), bind to all addresses on the interface rather than an arbitrary one. If the publish address is not specified, default it from the bound addresses based on the following sort ordering: * ipv4/ipv6 (java.net.preferIPv4Stack, defaults to true) * ordinary addresses * site-local addresses * link local addresses * loopback addresses One one address is published, and multicast is still always over ipv4: these need to be future improvements. Closes #12906 Closes #12915 Squashed commit of the following: commit 7e60833312f329a5749f9a256b9c1331a956d98f Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 14:45:33 2015 -0400 fix java 7 compilation oops commit c7b9f3a42058beb061b05c6dd67fd91477fd258a Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 14:24:16 2015 -0400 Cleanup/fix logic around custom resolvers commit bd7065f1936e14a29c9eb8fe4ecab0ce512ac08e Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 13:29:42 2015 -0400 Add some unit tests for utility methods commit 0faf71cb0ee9a45462d58af3d1bf214e8a79347c Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 12:11:48 2015 -0400 localhost all the way down commit e198bb2bc0d1673288b96e07e6e6ad842179978c Merge: b55d092 b93a75f Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 12:05:02 2015 -0400 Merge branch 'master' into network_cleanup commit b55d092811d7832bae579c5586e171e9cc1ebe9d Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 12:03:03 2015 -0400 fix docs, fix another bug in multicast (publish host = bad here!) commit 88c462eb302b30a82585f95413927a5cbb7d54c4 Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 11:50:49 2015 -0400 remove nocommit commit 89547d7b10d68b23d7f24362e1f4782f5e1ca03c Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 11:49:35 2015 -0400 fix http too commit 9b9413aca8a3f6397b5031831f910791b685e5be Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 11:06:02 2015 -0400 Fix transport / interface code Next up: multicast and then http
2015-08-17 15:37:07 -04:00
2015-12-10 05:24:25 -05:00
`_local_`::
Fix network binding for ipv4/ipv6 When elasticsearch is configured by interface (or default: loopback interfaces), bind to all addresses on the interface rather than an arbitrary one. If the publish address is not specified, default it from the bound addresses based on the following sort ordering: * ipv4/ipv6 (java.net.preferIPv4Stack, defaults to true) * ordinary addresses * site-local addresses * link local addresses * loopback addresses One one address is published, and multicast is still always over ipv4: these need to be future improvements. Closes #12906 Closes #12915 Squashed commit of the following: commit 7e60833312f329a5749f9a256b9c1331a956d98f Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 14:45:33 2015 -0400 fix java 7 compilation oops commit c7b9f3a42058beb061b05c6dd67fd91477fd258a Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 14:24:16 2015 -0400 Cleanup/fix logic around custom resolvers commit bd7065f1936e14a29c9eb8fe4ecab0ce512ac08e Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 13:29:42 2015 -0400 Add some unit tests for utility methods commit 0faf71cb0ee9a45462d58af3d1bf214e8a79347c Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 12:11:48 2015 -0400 localhost all the way down commit e198bb2bc0d1673288b96e07e6e6ad842179978c Merge: b55d092 b93a75f Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 12:05:02 2015 -0400 Merge branch 'master' into network_cleanup commit b55d092811d7832bae579c5586e171e9cc1ebe9d Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 12:03:03 2015 -0400 fix docs, fix another bug in multicast (publish host = bad here!) commit 88c462eb302b30a82585f95413927a5cbb7d54c4 Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 11:50:49 2015 -0400 remove nocommit commit 89547d7b10d68b23d7f24362e1f4782f5e1ca03c Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 11:49:35 2015 -0400 fix http too commit 9b9413aca8a3f6397b5031831f910791b685e5be Author: Robert Muir <rmuir@apache.org> Date: Mon Aug 17 11:06:02 2015 -0400 Fix transport / interface code Next up: multicast and then http
2015-08-17 15:37:07 -04:00
2015-12-10 05:24:25 -05:00
Any loopback addresses on the system, for example `127.0.0.1`.
2015-12-10 05:24:25 -05:00
`_site_`::
2015-12-10 05:24:25 -05:00
Any site-local addresses on the system, for example `192.168.0.1`.
`_global_`::
Any globally-scoped addresses on the system, for example `8.8.8.8`.
[float]
2015-12-10 05:24:25 -05:00
==== IPv4 vs IPv6
These special values will work over both IPv4 and IPv6 by default, but you can
also limit this with the use of `:ipv4` of `:ipv6` specifiers. For example,
`_en0:ipv4_` would only bind to the IPv4 addresses of interface `en0`.
[TIP]
.Discovery in the cloud
================================
More special settings are available when running in the cloud with either the
{plugins}/discovery-ec2.html[EC2 discovery plugin] or the
2015-12-10 05:24:25 -05:00
{plugins}/discovery-gce-network-host.html#discovery-gce-network-host[Google Compute Engine discovery plugin]
installed.
================================
[float]
[[advanced-network-settings]]
=== Advanced network settings
2015-12-10 05:24:25 -05:00
The `network.host` setting explained in <<common-network-settings,Commonly used network settings>>
is a shortcut which sets the _bind host_ and the _publish host_ at the same
time. In advanced used cases, such as when running behind a proxy server, you
may need to set these settings to different values:
`network.bind_host`::
2015-12-10 05:24:25 -05:00
This specifies which network interface(s) a node should bind to in order to
listen for incoming requests. A node can bind to multiple interfaces, e.g.
two network cards, or a site-local address and a local address. Defaults to
`network.host`.
2015-12-10 05:24:25 -05:00
`network.publish_host`::
The publish host is the single interface that the node advertises to other nodes
in the cluster, so that those nodes can connect to it. Currently an
Elasticsearch node may be bound to multiple addresses, but only publishes one.
If not specified, this defaults to the ``best'' address from `network.host`,
sorted by IPv4/IPv6 stack preference, then by reachability. If you set a
`network.host` that results in multiple bind addresses yet rely on a specific
address for node-to-node communication, you should explicitly set
`network.publish_host`.
2015-12-10 05:24:25 -05:00
Both of the above settings can be configured just like `network.host` -- they
accept IP addresses, host names, and
<<network-interface-values,special values>>.
[float]
[[tcp-settings]]
=== Advanced TCP Settings
2015-12-10 05:24:25 -05:00
Any component that uses TCP (like the <<modules-http,HTTP>> and
<<modules-transport,Transport>> modules) share the following settings:
[horizontal]
`network.tcp.no_delay`::
2015-12-10 05:24:25 -05:00
Enable or disable the https://en.wikipedia.org/wiki/Nagle%27s_algorithm[TCP no delay]
setting. Defaults to `true`.
`network.tcp.keep_alive`::
Enable or disable https://en.wikipedia.org/wiki/Keepalive[TCP keep alive].
Defaults to `true`.
2015-12-10 05:24:25 -05:00
`network.tcp.reuse_address`::
Should an address be reused or not. Defaults to `true` on non-windows
machines.
2015-12-10 05:24:25 -05:00
`network.tcp.send_buffer_size`::
2015-12-10 05:24:25 -05:00
The size of the TCP send buffer (specified with <<size-units,size units>>).
By default not explicitly set.
2015-12-10 05:24:25 -05:00
`network.tcp.receive_buffer_size`::
The size of the TCP receive buffer (specified with <<size-units,size units>>).
By default not explicitly set.
[float]
2015-12-10 05:24:25 -05:00
=== Transport and HTTP protocols
An Elasticsearch node exposes two network protocols which inherit the above
settings, but may be further configured independently:
TCP Transport::
Used for communication between nodes in the cluster, by the Java
{javaclient}/transport-client.html[Transport client].
See the <<modules-transport,Transport module>> for more information.
2015-12-10 05:24:25 -05:00
HTTP::
Exposes the JSON-over-HTTP interface used by all clients other than the Java
clients. See the <<modules-http,HTTP module>> for more information.