On Fri, Mar 13, 2015 at 6:09 AM, Michael McCandless <[email protected]> wrote: > That is the right setting to disable store throttling, but even without > throttling writes MB/sec for merges, the merges can still fall behind, > leading to index throttling. ES does this to protect the health of the index > because too many segments will cause all sorts of trouble. > > What IO system is your index on? If you're on spinning disks you could try > setting index.merge.scheduler.max_thread_count to 1 since spinning disks > struggle with concurrent merges. See > http://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-merge.html > > Also, do you leave enough (at least 50%) free RAM to the OS for buffering > pages? This can make a difference with spinning disks since the OS has more > freedom to do read-ahead on the files being merged...
The index is on an SSD (EC2 m3.large). I'll look into what else is going on, had just noticed a few of those log entries, and thought setting `indices.store.throttle.type: none` might be a quick fix :-) -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHte5%2B%2BqrQzoQAicwz9Q%2BMprcNVhVqXWKGp_CkKYefKNeWnO_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
