-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Clarify G1GC support on docs #43885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Pinging @elastic/es-docs |
Pinging @elastic/es-core-infra |
Related: #41358 |
[docs issue triage] Leaving this open as it's still relevant. |
@jrodewig @debadair Is this issue still relevant? It looks like we have some discussion of garbage collectors on the page about the serial collector check: https://www.elastic.co/guide/en/elasticsearch/reference/7.10/_use_serial_collector_check.html That paragraph mentions that we default to using G1GC, and that CMS will only be used if you don't use the JVM shipped with Elasticsearch. |
Thanks for the ping @williamrandolph. I'm going to close this issue. With #49123, we now default to G1GC for JDK 14+. With #59667, Elasticsearch 7.11+ ergonomically adjusts G1GC options based on heap size. While users can manually adjust G1GC options, I don't think we should encourage it or document it in depth. That effort can be covered in #53889. |
As of 6.5.0, G1GC is now supported by Elasticsearch.
We should document this, perhaps in the setup page.
The text was updated successfully, but these errors were encountered: