# NoNodeAvailableException **URL:** \ **Category:** Elasticsearch\ **Created:** [August 17, 2012, 12:43am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765 "2012-08-17T00:43:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Scott\_2](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@Scott\_2](https://discuss.elastic.co/u/Scott_2)\ **Post date:** [August 17, 2012, 12:43am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/1 "2012-08-17T00:43:12Z")
Version 0.19.4. We are getting this exception occasionally, on the client that is performing searches. There is no indexing going on at this time. Having read through the previous messages, the first thing was to turn on debug logging for org.elasticsearch.client.transport. I did that, but am not seeing any messages in the log file pertaining to the error. I am getting these messages in my log file, so I'm sure I have debug logging turned on. DEBUG 18:27:33 [transport:94] [Devil-Slayer] node\_sampler\_interval[5s] DEBUG 18:27:33 [transport:94] [Devil-Slayer] adding address [[#transport#-1][inet[localhost/127.0.0.1:9300]]] What would cause this error, but not write to the log? Any help or pointers are appreciated. I'm a newbie with ES. -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 17, 2012, 1:50am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/2 "2012-08-17T01:50:25Z")
Are you running ES node and your client on the same machine? Is your client application create a new node (and client) at each search? I don't understand your setup. David 😉 Twitter : @dadoonet / @elasticsearchfr Le 17 août 2012 à 02:43, scott [scott@tempo.ai](mailto:scott@tempo.ai) a écrit : > Version 0.19.4. > > We are getting this exception occasionally, on the client that is performing searches. There is no indexing going on at this time. > > Having read through the previous messages, the first thing was to turn on debug logging for org.elasticsearch.client.transport. I did that, but am not seeing any messages in the log file pertaining to the error. I am getting these messages in my log file, so I'm sure I have debug logging turned on. > > DEBUG 18:27:33 [transport:94] [Devil-Slayer] node\_sampler\_interval[5s] > > DEBUG 18:27:33 [transport:94] [Devil-Slayer] adding address [[#transport#-1][inet[localhost/127.0.0.1:9300]]] > > What would cause this error, but not write to the log? Any help or pointers are appreciated. I'm a newbie with ES. > > -- -- ---
**Author:** ![Scott\_2](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@Scott\_2](https://discuss.elastic.co/u/Scott_2)\ **Post date:** [August 17, 2012, 1:58am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/3 "2012-08-17T01:58:43Z")
Server and client are on different machines. Client creates a TransportClient once and the same TransportClient gets reused for the lifetime of the client application. We currently have up to 10 different threads executing searches against the same TransportClient. -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 17, 2012, 2:02am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/4 "2012-08-17T02:02:03Z")
So your error comes when you restart your client application? -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 17 août 2012 à 03:58, scott [scott@tempo.ai](mailto:scott@tempo.ai) a écrit : > Server and client are on different machines. > > Client creates a TransportClient once and the same TransportClient gets reused for the lifetime of the client application. > > ## We currently have up to 10 different threads executing searches against the same TransportClient. -- ---
**Author:** ![Scott\_2](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@Scott\_2](https://discuss.elastic.co/u/Scott_2)\ **Post date:** [August 17, 2012, 2:02am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/5 "2012-08-17T02:02:10Z")
I reread my original post and understand your confusion. The log file entries I copied were from a unit test and that does run on one machine. However, we only have the issue when we push to our test environment, which puts the server and client on separate machines. Sorry. -- ---
**Author:** ![Scott\_2](https://avatars.discourse-cdn.com/v4/letter/s/e274bd/32.png) [@Scott\_2](https://discuss.elastic.co/u/Scott_2)\ **Post date:** [August 17, 2012, 2:07am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/6 "2012-08-17T02:07:37Z")
No, the app starts fine and runs several successful queries. The error happens occasionally. Not all the time. I bumped the client.transport.ping\_timeout to 10 seconds, but we are still occasionally seeing the errors. -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 17, 2012, 2:08am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/7 "2012-08-17T02:08:48Z")
Ok. That means that you never succeed in connecting your client and your node in your test env? If so, check your firewall settings (open 9300 port). -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 17 août 2012 à 04:02, scott [scott@tempo.ai](mailto:scott@tempo.ai) a écrit : > I reread my original post and understand your confusion. The log file entries I copied were from a unit test and that does run on one machine. However, we only have the issue when we push to our test environment, which puts the server and client on separate machines. > > Sorry. > > -- -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 17, 2012, 2:12am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/8 "2012-08-17T02:12:48Z")
Try to update to 0.19.8 as there are some issues about nodes fixed in 0.19.5 although I don't think you get the same issue. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 17 août 2012 à 04:07, scott [scott@tempo.ai](mailto:scott@tempo.ai) a écrit : > No, the app starts fine and runs several successful queries. The error happens occasionally. Not all the time. > > I bumped the client.transport.ping\_timeout to 10 seconds, but we are still occasionally seeing the errors. > > -- -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:16am UTC](https://discuss.elastic.co/t/nonodeavailableexception/8765/9 "2017-07-06T03:16:07Z")