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