Update for clarification
Make it clear which nodes in the cluster should have `http.enabled` set to `false`. Closes #10305
This commit is contained in:
parent
589f8d4468
commit
ae60144123
|
@ -90,7 +90,11 @@ It also uses the common
|
||||||
=== Disable HTTP
|
=== Disable HTTP
|
||||||
|
|
||||||
The http module can be completely disabled and not started by setting
|
The http module can be completely disabled and not started by setting
|
||||||
`http.enabled` to `false`. This make sense when creating non
|
`http.enabled` to `false`. Elasticsearch nodes (and Java clients) communicate
|
||||||
<<modules-node,data nodes>> which accept HTTP
|
internally using the <<modules-transport,transport interface>>, not HTTP. It
|
||||||
requests, and communicate with data nodes using the internal
|
might make sense to disable the `http` layer entirely on nodes which are not
|
||||||
<<modules-transport,transport>>.
|
meant to serve REST requests directly. For instance, you could disable HTTP on
|
||||||
|
<<modules-node,data-only nodes>> if you also have
|
||||||
|
<<modules-node,client nodes>> which are intended to serve all REST requests.
|
||||||
|
Be aware, however, that you will not be able to send any REST requests (eg to
|
||||||
|
retrieve node stats) directly to nodes which have HTTP disabled.
|
||||||
|
|
Loading…
Reference in New Issue