Dear Binh Ly, Thanks for your reply and sorry for not responding earlier. We've moved over our elasticsearch to SSD and I had hoped that that might help with the performance issues, but no luck.
It seems that whenever elastic is freshly started it performs pretty well, but after a couple days it just becomes really slow and seems to be having memory issues. > On Friday, February 7, 2014 6:43:08 PM UTC+1, Binh Ly wrote: > Yes it is possible that you have memory pressure. I'd probably: > 1) Set bootstrap.mlockall: true in the elasticsearch.yml file > 2) Once you're up and running (or when these GC pauses start to happen), check the node stats to see what you have in memory: > curl "http://localhost:9200/_nodes/stats/jvm?pretty"; > That will give you a rough idea if you might need to bump that ES_HEAP_SIZE up some more (up to 1/2 of your available RAM or 30GB whichever is smaller). The server has 40G heap size (increased from 30) on a virtual machine with 56G in total, and mlockall is true. The machine is not swapping (it only runs elastic and nginx/uwsgi). We are still using 0.9.10 on the production server, I can switch that over to 1.x to see if it helps. stats.json and the relevant config and log files are posted at https://gist.github.com/vanatteveldt/10717100 > 3) If you're reaching the limits of RAM on a single node, then it might be time to add more nodes to distribute those shards out horizontally. Yeah I guess that would be the ultimate remedy, but I don't really have budget at the moment to add servers. Thanks for any help, Wouter -- 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/4fdf044b-4668-4b0e-8f53-ae86dbdd846b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
