-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Prepare for removal of the CMS garbage collector #46973
Comments
Pinging @elastic/es-core-infra |
I did a few experiments with jdk13 G1GC, running
|
Logs for |
Tried |
when Parallel GC does finish, indexing and queries seem to be faster for 1g heap:
nyc_taxis 1G heap G1GC vs Parallel:
|
1G heap experiments: |
Thanks for doing these experiments Evgenia! IMHO we should be good for now with what we have and we can tackle this question separately at a later point. I'd expect that ParallelGC would require us to investigate thoroughly also on other fronts to ensure cluster stability as this collector is working quite differently than CMS and G1 (it's blocking instead of concurrent). |
) Relates to #46973 Co-authored-by: Evgenia Badyanova <[email protected]>
) Relates to #46973 Co-authored-by: Evgenia Badyanova <[email protected]>
Context
According to JEP 363 (originally draft JEP 8229049) the CMS garbage collector will be removed from OpenJDK (discussion of the patch and commit). The corresponding discussion on the OpenJDK mailing list mentions JDK 14 as targeted JDK. There is currently no release date for JDK 14 but based on past release cadence we should expect it to be released in late March 2020. As Elasticsearch currently recommends the CMS garbage collector we should be prepared for its removal. I'm raising this issue as a meta-issue to collect our thoughts on what is missing to run Elasticsearch with a different garbage collector than CMS out of the box.
Prior work
We have already investigated G1GC as an alternative garbage collector for Elasticsearch in #33685 and have recently adjusted the out-of-the box settings in #46169 to improve the effectiveness of Elasticsearch's real-memory circuit breaker with G1GC.
Tasks
The following list may be incomplete, please add new tasks as needed:
The text was updated successfully, but these errors were encountered: