# Single Node Configuration Advice

**URL:** <https://discuss.elastic.co/t/single-node-configuration-advice/22832>\
**Category:** Elasticsearch\
**Created:** [March 23, 2015, 6:34pm UTC](https://discuss.elastic.co/t/single-node-configuration-advice/22832 "2015-03-23T18:34:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vindictive27](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vindictive27/32/807_2.png) [@vindictive27](https://discuss.elastic.co/u/vindictive27)\
**Post date:** [March 23, 2015, 6:34pm UTC](https://discuss.elastic.co/t/single-node-configuration-advice/22832/1 "2015-03-23T18:34:06Z")

</div>

Hello,

I've searched through the group here and found a lot of information, but I  
am hoping someone could help me verify my configuration - as I have been  
running into many issues running ES.

I have a very simple setup with a small number of documents and only one  
index (currently about 100 documents in the index).

Over time, the search becomes unresponsive and ultimately hangs or crashes,  
and I haven't been able to pinpoint the exact reason because there are  
20-30 different random debug/error messages in the logs.

What I have for my elasticsearch.yml:

node.local: true  
discovery.zen.ping.multicast: false  
threadpool.search.type: cached  
#network.bind\_host: _local_  
#network.publish\_host: _non\_loopback_  
#network.host: localhost

The only thing I have set in my elasticsearch.conf:

ES\_HEAP\_SIZE=8g

I am running ES 1.4.2 on an Ubuntu VM (SSD, 14gb RAM, 2 CPU) out on Azure,  
I also have the Marvel plug-in installed, and latest JVM.

The index size is about 1 megabyte (the marvel indexes are there too and  
larger - this is just the index I created and maintain).

Using the NEST API through .NET for indexing, searching, and deleting.

The reason i have the threadpool.search.type: cached setting is because the  
most recent error I was getting had to do with reaching a queue capacity  
limit of 1000.

Restarting ES fixes it every time it hangs/crashes - but it only lasts a  
day or so then it crashes again.

Any help would be appreciated.

--  
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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/efb95688-1023-47d9-8545-e8e9ea026273%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/efb95688-1023-47d9-8545-e8e9ea026273%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 24, 2015, 12:02am UTC](https://discuss.elastic.co/t/single-node-configuration-advice/22832/2 "2015-03-24T00:02:51Z")

</div>

How much data overall do you have?  
If you are getting queue capacity limits then chances are you're  
overloading your instance.

On 24 March 2015 at 05:34, vindictive27 [vindictive27@gmail.com](mailto:vindictive27@gmail.com) wrote:

> Hello,
> 
> I've searched through the group here and found a lot of information, but I  
> am hoping someone could help me verify my configuration - as I have been  
> running into many issues running ES.
> 
> I have a very simple setup with a small number of documents and only one  
> index (currently about 100 documents in the index).
> 
> Over time, the search becomes unresponsive and ultimately hangs or  
> crashes, and I haven't been able to pinpoint the exact reason because there  
> are 20-30 different random debug/error messages in the logs.
> 
> What I have for my elasticsearch.yml:
> 
> node.local: true  
> discovery.zen.ping.multicast: false  
> threadpool.search.type: cached  
> #network.bind\_host: _local_  
> #network.publish\_host: _non\_loopback_  
> #network.host: localhost
> 
> The only thing I have set in my elasticsearch.conf:
> 
> ES\_HEAP\_SIZE=8g
> 
> I am running ES 1.4.2 on an Ubuntu VM (SSD, 14gb RAM, 2 CPU) out on Azure,  
> I also have the Marvel plug-in installed, and latest JVM.
> 
> The index size is about 1 megabyte (the marvel indexes are there too and  
> larger - this is just the index I created and maintain).
> 
> Using the NEST API through .NET for indexing, searching, and deleting.
> 
> The reason i have the threadpool.search.type: cached setting is because  
> the most recent error I was getting had to do with reaching a queue  
> capacity limit of 1000.
> 
> Restarting ES fixes it every time it hangs/crashes - but it only lasts a  
> day or so then it crashes again.
> 
> Any help would be appreciated.
> 
> --  
> 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/efb95688-1023-47d9-8545-e8e9ea026273%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/efb95688-1023-47d9-8545-e8e9ea026273%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/efb95688-1023-47d9-8545-e8e9ea026273%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/efb95688-1023-47d9-8545-e8e9ea026273%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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9ULLcF%3DRN280y0wAKFumXqqphRHj72DZBWxXAGnP2Vhg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9ULLcF%3DRN280y0wAKFumXqqphRHj72DZBWxXAGnP2Vhg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:24am UTC](https://discuss.elastic.co/t/single-node-configuration-advice/22832/3 "2017-07-06T00:24:39Z")

</div>

Closed on July 6, 2017, 12:24am UTC


