Hey all, we regularly (several times a week) get longish GCs (20s or more) due to promotion failures.
>From what I understand this type of major GC is caused by fragmentation of the heap. So I'm wondering: 1. What is all the stuff ES puts into the heap that ends up in the Old Gen? 2. Are there any recommended strategies for dealing with this specific kind of problem. For example, would allowing more filter caching help or cause even more problems? And so on. To give a little more info on our usage, we're read heavy, nearly entirely filter operations. Our heap is at ~10g. nearly all of which is used by the Old Gen (until a major GC runs). -- 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/4b3ef926-94b7-4de0-b076-d5fdbc44021c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
