FWIW, we saw many long running GC events using the default GC manager - changing to G1 solved most of the problems ( at the expense of slightly higher CPU all the time).... After that you can take the longer road to debugging memory allocation for your use case :-) On 18/11/2014 6:21 am, "Wilfred Hughes" <[email protected]> wrote:
> We're running elasticsearch 1.2.4 on Java 1.7.0_40, for what it's worth. > > -- > 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/44213a82-7604-430c-9017-8d4398f9694d%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/44213a82-7604-430c-9017-8d4398f9694d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CACj2-4K5uo6BRnEhxv109gorBigVTzoCt_Fcjqgv5BYXA70u5A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
