I myself prefer TransportClient as it has absolutely no impact on the cluster state. A new node joining the cluster generates a cluster state update which is propagated to all nodes.
I prefer having a very stable cluster state than continuous updates. Think about a Java batch which starts every minute and connect to the cluster to perform whatever action. That would be a lot of events per day. That’s why I mostly prefer using TransportClient. My 2 cents. -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr <https://twitter.com/elasticsearchfr> | @scrutmydocs <https://twitter.com/scrutmydocs> > Le 5 janv. 2015 à 19:15, Vijay Tiwary <vijaykr.tiw...@gmail.com> a écrit : > > Thanks David once again. Can you please help in deciding which one should I > go for NodeClient or TransportClient for production deployments. > From the elastic search documentation what I understand is that Node client > eliminates the double hop that is present in Transport Client. Shall I opt > for Node client then? Please suggest. > > On Monday, January 5, 2015 8:17:40 PM UTC+5:30, David Pilato wrote: > If you don’t want to define transport addresses, you’d better use a > NodeClient. > A NodeClient is actually a node running inside the cluster (with auto > discovery…) but without any data. > > You just need to provide the cluster name with a NodeClient. See > http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html#node-client > > <http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html#node-client> > > > -- > David Pilato | Technical Advocate | Elasticsearch.com > <http://elasticsearch.com/> > @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr > <https://twitter.com/elasticsearchfr> | @scrutmydocs > <https://twitter.com/scrutmydocs> > > > >> Le 5 janv. 2015 à 13:46, Vijay Tiwary <vijaykr...@gmail.com <javascript:>> a >> écrit : >> >> I am trying to connect remotely to elastic search cluster having 2 nodes >> My question is I am able to query successfully only when we configure both >> the cluster name and host name of the individual nodes? Why it doesn't work >> if I only configure the cluster name in my client code >> >> Settings settings = ImmutableSettings.settingsBuilder() >> .put("cluster.name <http://cluster.name/>", "myClusterName").build(); >> Client client = new TransportClient(settings ).addTransportAddress(new >> InetSocketTransportAddress("host1", 9300)) >> .addTransportAddress(new InetSocketTransportAddress("host2", 9300)); >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/dd201d66-71b4-4d74-bb99-255144a083a2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/dd201d66-71b4-4d74-bb99-255144a083a2%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com > <mailto:elasticsearch+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/98810b45-e4b5-4776-ac45-ba6b41adeff9%40googlegroups.com > > <https://groups.google.com/d/msgid/elasticsearch/98810b45-e4b5-4776-ac45-ba6b41adeff9%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9740D8FF-F93A-4C5B-92E9-15602E1701FF%40pilato.fr. For more options, visit https://groups.google.com/d/optout.