My scenario: I am using the java TransportClient 18.7 in my Play! application to query elasticsearch 18.6. My questions: It is logging messages that look like it is acting like a node, based on the "[Nodename]" in the message. I thought TransportClient did not join as a node? What is happenin…

TransportClient logs errors as if it was a node?

Mark_Waddle (Mark Waddle) January 20, 2012, 2:52am 3

Oh ya, that's it. I'm closing the client. Guess I should have realized that
one. Thanks!

Topic		Replies	Views
TransportClient and NoNodeAvailableException Elasticsearch	6	640	July 6, 2017
NoNodeAvailableException Elasticsearch	8	470	July 6, 2017
No node available Exception Elasticsearch	10	7487	July 6, 2017
NoNodeException Error when trying to create a transport client for Elasticsearch Elasticsearch	10	3246	July 5, 2017
Newbie question for TransportClient Elasticsearch	9	367	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

TransportClient logs errors as if it was a node?

Related topics