The queries that we run seem to be very CPU Intensive and cause the Servers
to max out within a short amount of time. On debugging, it looks like
standard queries take too long to respond too.
We are currently running version 1.0.2 of Elasticsearch and have about
67.3G of data on Production. There are currently 5 Shards running on 2
Nodes (1 Replica). There is a total of 252gb RAM with Heap Size set to
The Indexing rate is high since we are migrating data:
The Refresh Activity report from ElasticHQ:
The Match All Query takes a whopping 520 - 680ms to run.
However, on a similar Test Environment Setup (with 8G of data), the same
query takes about 80-120ms to execute. Which feels more like the average.
What are some of the recommendations that can improve this bottleneck? Will
adding more Nodes help alleviate this issue or will it worsen it.
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66c26a89-b3f8-4a8c-96dc-45babc1e012d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.