-
Notifications
You must be signed in to change notification settings - Fork 25.2k
GC rate increases randomly, increasing the cpu to 100%, dropping indexing rate in v8.11.3 #103779
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-core-infra (Team:Core/Infra) |
The comment says it is 8.11.0, but the given version is 8.11.3. Which version is being used here? |
We actually tried both, similar behaviour, we are currently at 8.11.3, i have edited the description. thanks for pointing out. |
There are known issues with GC on JDK 20+, see #99592. We have merged improvements into 8.11.2 that improve matters, but (as you've noticed) don't fix the issue entirely. The exact effect depends on your specific use & indexing patterns. A heap dump might help with determining if there's something else going on that is exacerbating the GC issues. The best bet is to run on JDK17, if possible, and keep watch on #99592 |
We are running this cluster on k8s with ECK operator, as it really doesn't let us downgrade, could you please help in how can we use JDK20 or JDK17 with v8.11.3 ELK.
I couldn't find anything around this in ECK docs |
Hello team, any help on above, or any config changes we can do to mitigate this issue ? |
can you share gc.log??the chart line broken cause by reboot ?? |
yes, the broken chart line is caused by reboot, GC rate continuosly increases, here is snippet from when it was breaking down.
|
Hello Team, any help on above, or any config changes we can do to mitigate this issue ? |
1 similar comment
Hello Team, any help on above, or any config changes we can do to mitigate this issue ? |
We have recently released 8.12, which includes various changes aimed at improving the behaviour of the GC on recent JDKs. I suggest upgrading to 8.12 to see what improvement that gives your particular use case. |
Hi, I don't see anything in the release notes that mentions JVM or JDK or GC, and there's no update on the issue #99592. Is there some other bug we should be following, or another list of relevant updates? |
Hello @thecoop , we have upgraded to 8.12.0 now and I will update more on this ticket if we see improvements. |
Hello @thecoop We have not seen any crashes since upgrade to 8.12.0, and it's been more than a week. ( while earlier it was crashing everyday ) i think this solves the problem. Thanks for your help :) |
Elasticsearch Version
8.11.3
Installed Plugins
No response
Java Version
bundled
OS Version
Linux oke-cbamoicz23a-ndvldsi765q-skex3d2ztgq-6 5.4.17-2136.305.5.3.el8uek.x86_64 #2 SMP Thu Mar 17 10:45:33 PDT 2022 x86_64 x86_64 x86_64 GNU/Linux
Problem Description
We were on version 8.7.0 from last few months and we saw no issues at all, cpu was always less then 30% overall.
our indexing rate stays around 25K/s Total, 12K/s primaries. search rate around 200/s. the cluster stores around 6TB of data at a time, 4500 shards.
We upgraded last week to 8.11.3, and the following issue started
We also saw an increase in bulk average size after upgrade

Steps to Reproduce
Upgrade ELK from 8.7.0 to 8.11.3
Logs (if relevant)
The text was updated successfully, but these errors were encountered: