I'm trying to tune ES for predictable response times under an update-heavy
load. Our big challenge has been long GC pauses (sometimes stopping the app
for up to 30 seconds).
by Jörg Prante has a lot of knowledgable advice on GC tuning and seems to
endorse the G1 GC for the situation I'm working with. It appears to reduces
long pauses at the expense of higher CPU load, which sounds like just the
trade-off I want to make.
But when I try to run the G1 GC, it causes the JVM to segfault, pretty soon
after starting. I've asked around with a few others in #elasticsearch, and
it seems others are having similar issues with G1--many I've spoken to have
tried it but ditched it when it segfaulted too much.
However, everyone seems to "know somebody" or know of someone who has had
success with G1.
So ... is G1 working for anyone? If you have G1 working and no segfault
issues, can you tell me a little more about your environment? (what OS,
JVM, ES version, JVM flags, app settings etc.) It doesn't make sense to me
that it is segfaulting and dying for me and others, but working okay for
some. There has to be a reason, if it is working for some--I'm growing
skeptical that G1GC is working for anyone until I hear otherwise
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@example.com.
For more options, visit https://groups.google.com/groups/opt_out.