# NoNodeAvailable exception: amazon EBS deployment of elasticsearch

**URL:** <https://discuss.elastic.co/t/nonodeavailable-exception-amazon-ebs-deployment-of-elasticsearch/9409>\
**Category:** Elasticsearch\
**Created:** [October 18, 2012, 2:58pm UTC](https://discuss.elastic.co/t/nonodeavailable-exception-amazon-ebs-deployment-of-elasticsearch/9409 "2012-10-18T14:58:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Sanwald](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_sanwald/32/2076_2.png) [@Paul\_Sanwald](https://discuss.elastic.co/u/Paul_Sanwald)\
**Post date:** [October 18, 2012, 2:58pm UTC](https://discuss.elastic.co/t/nonodeavailable-exception-amazon-ebs-deployment-of-elasticsearch/9409/1 "2012-10-18T14:58:45Z")

</div>

Hey Everyone,  
I have an elasticsearch cluster set up on amazon's elastic beanstalk  
infrastructure; it's deployed in a tomcat7 container, and using  
elasticsearch.wares to fire up a node. my configuration is pretty much from  
this tutorial.

I have been load testing the system, and periodically, I get a  
"NoNodeAvailable" exception. I turned on debug level logging for  
org.elasticsearch, and here's what I see. I've implemented some retry logic  
as a band-aid, but it doesn't fix the problem 100%, and it feels like a  
band aid.

I haven't been able to reproduce this problem locally. Does anyone have an  
idea of what might be happening here?

14:47:37,155 INFO fetch:104 - [Angel Dust] [content][4] took[61.4micros],  
took\_millis[0], search\_type[QUERY\_THE  
N\_FETCH], total\_shards[5],  
source[{"from":0,"size":100,"query":{"bool":{"must":{"bool":{"should":{"match":{"body  
":{"query":"biscuits","type":"boolean"}}}}}}}}], extra\_source[],  
_14:47:37,171 DEBUG netty:94 - [Speed Demon] disconnected from  
[[#transport#-1][inet[redowl-refdata-service.elast_  
_[icbeanstalk.com/23.23.118.78:9300](http://icbeanstalk.com/23.23.118.78:9300)]]]_  
14:47:37,295 INFO SearchContentResource:114 - Exception happened whilst  
searching for  
actors: [],  
keywords [enron],  
eventStartInSeconds: null,  
durationInSeconds: null  
java.util.concurrent.ExecutionException:  
org.elasticsearch.client.transport.NoNodeAvailableException: No node av  
ailable  
at  
org.elasticsearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:285)  
at  
org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:272)

I then see some successful queries on different nodes:  
4:47:37,387 INFO query:104 - [Angel Dust] [content][3] took[8.8ms],  
took\_millis[8], search\_type[QUERY\_THEN\_FETCH], total\_shards[5],  
source[{"from":0,"size":100,"query":{"bool":{"must":{"bool":{"should":{"match":{"body":{"query":"enron","type":"boolean"}}}}}}}}],  
extra\_source[],

and then, a reconnect:

\*14:47:38,200 DEBUG netty:94 - [Speed Demon] connected to node  
[[#transport#-1][inet[[redowl-refdata-service.elasticbeanstalk.com/23.23.118.78:9300](http://redowl-refdata-service.elasticbeanstalk.com/23.23.118.78:9300)]]]  
\*

Thanks for any thoughts you may have. Elastic Search is working fantastic  
for most cases, it's just this one error we uncovered during load testing.

Best,

--paul

--

---

<div class="post-metadata">

**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:08am UTC](https://discuss.elastic.co/t/nonodeavailable-exception-amazon-ebs-deployment-of-elasticsearch/9409/2 "2017-07-06T03:08:05Z")

</div>