From 26863a4d75269a36ff617ec6dcdb561499ed3212 Mon Sep 17 00:00:00 2001 From: David Pilato Date: Mon, 29 Feb 2016 17:29:12 +0100 Subject: [PATCH] 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 --- docs/reference/modules/network.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/modules/network.asciidoc b/docs/reference/modules/network.asciidoc index 922b00bcc63..6657e98869f 100644 --- a/docs/reference/modules/network.asciidoc +++ b/docs/reference/modules/network.asciidoc @@ -163,9 +163,8 @@ settings, but may be further configured independently: TCP Transport:: -Used for communication between nodes in the cluster and by the Java -{javaclient}/node-client.html[Node client], -{javaclient}/transport-client.html[Transport client], and by the +Used for communication between nodes in the cluster, by the Java +{javaclient}/transport-client.html[Transport client] and by the <>. See the <> for more information.