honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove indication of future multi-homing support (#32187) 

We do not support intra-cluster connections on multiple interfaces, but the
documentation indicates that we will in future. In fact there is currently no
plan to support this, so the forward-looking documentation is misleading. This
commit

- removes the misleading sentence
- fixes that a transport profile affects outbound connections, not inbound ones
- tidies up some nearby text
This commit is contained in:
David Turner 2018-07-19 11:33:46 +01:00 committed by GitHub
parent f7da55aa3c
commit f6d7854f76
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/reference/modules/transport.asciidoc
View File

@ -59,7 +59,8 @@ It also uses the common
[float]
==== TCP Transport Profiles
Elasticsearch allows you to bind to multiple ports on different interfaces by the use of transport profiles. See this example configuration
Elasticsearch allows you to bind to multiple ports on different interfaces by
the use of transport profiles. See this example configuration
[source,yaml]
--------------
@ -71,10 +72,12 @@ transport.profiles.dmz.port: 9700-9800
transport.profiles.dmz.bind_host: 172.16.1.2
--------------
The `default` profile is a special. It is used as fallback for any other profiles, if those do not have a specific configuration setting set.
Note that the default profile is how other nodes in the cluster will connect to this node usually. In the future this feature will allow to enable node-to-node communication via multiple interfaces.
The `default` profile is special. It is used as a fallback for any other
profiles, if those do not have a specific configuration setting set, and is how
this node connects to other nodes in the cluster.
The following parameters can be configured like that
The following parameters can be configured on each transport profile, as in the
example above:
* `port`: The port to bind to
* `bind_host`: The host to bind