When your indexing pauses, do you know how your JVM (the one ES is in) is
behaving in terms of GCing? That's one thing to check. I believe there
are a couple of settings that control flushing. Of course, you'll also
want to check that it's not the source of your data that is pausing, and
Increasing index.refresh_interval will help, too.
You'll also want to look at your 2 ES nodes and see if it's the CPU or disk
IO or network IO or JVM heap that's the bottleneck and based on that you
will know what options may have a positive effect.
We haven't announced SPM for ElasticSearch just yet and have not polished
it completely, but you are welcome to use our SPM for ElasticSearch
tool/service (it's free) that will expose a number of performance metrics
from ES and from the underlying JVM and the server itself, so you can more
easily tell what's going on with your ES cluster. SPM for ES is hiding at
Hiring ElasticSearch Engineers World-Wide --
On Tuesday, March 6, 2012 8:59:23 AM UTC+8, Oren Mazor wrote:
I have a 40m doc index across two fairly hefty machines (32gb ram, 4core).
I do around 100 indexes a second and maybe 30 deletes a second, all in
my settings are as follows:
I find I still see delays whenever my indexing spikes to around 500-1000/second, and I'm wondering what I can do take better use of these two nodes. the load on them is almost negligible at pretty much all times.
one thing I was thinking of doing is starting one or two more nodes on the same machine, and move some of those shards across (I use routing) to maybe help out with indexing that way.