Fix: Change docs on "node client" to not use an in-memory node
Currently we suggesting users create a Node (using NodeBuilder in 2.x) to have a client that is capable of keeping up-to-date information. This is generally a bad idea as it means elasticsearch has no control over eg max heap size or gc settings, and is also problematic for users because they must deal with dependency collisions (and in 2.x+ dependencies of elasticsearch itself). A better alternative, and what we should document, is to run a local elasticsearch server using bin/elasticsearch, and then use the transport client to connect to that local node. This local connection is virtually free, and allows the client code to be completely isolated from the elasticsearch process. Plugins are then also easy to deal with: just install them in elasticsearch as usual. Related to #16679
This commit is contained in:
parent
fd729604ab
commit
26863a4d75
|
@ -163,9 +163,8 @@ settings, but may be further configured independently:
|
||||||
|
|
||||||
TCP Transport::
|
TCP Transport::
|
||||||
|
|
||||||
Used for communication between nodes in the cluster and by the Java
|
Used for communication between nodes in the cluster, by the Java
|
||||||
{javaclient}/node-client.html[Node client],
|
{javaclient}/transport-client.html[Transport client] and by the
|
||||||
{javaclient}/transport-client.html[Transport client], and by the
|
|
||||||
<<modules-tribe,Tribe node>>. See the <<modules-transport,Transport module>>
|
<<modules-tribe,Tribe node>>. See the <<modules-transport,Transport module>>
|
||||||
for more information.
|
for more information.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue