-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Change severity of negative stats messages from WARN to DEBUG #60375
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
Conversation
Pinging @elastic/es-core-features (:Core/Features/Stats) |
@elasticmachine update branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks, @jbaiera! |
Why is this patch not backported to 6.8 |
elasticsearch 6.8.18 docker image, on one of my clusters, repeats this again and again, memory locked, so annoying:
|
same issue! |
I'm also seeing this in a 6.8.21 cloud deployment. |
We are suffering from this as well on a 6.8 ElasticCloud environment |
The 6.8.22 and later releases of Elasticsearch have this change. |
Because the incidence of negative stats values reported by the JVM has increased significantly as of JDK14 (at least partially due to this JVM bug: https://bugs.openjdk.java.net/browse/JDK-8242480), this message is ending up in logs fairly frequently and causing some concern and confusion among users. The message is largely harmless because the only effect is that the stats value, usually either free memory or free swap space, reported as negative by the OS will instead be recorded as zero by ES and no user action is necessary or possible. Should the JVM bug be fixed in the future, upgrading to an unaffected JVM may reduce the incidence of these occurrences.