-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Support for Heap after GC stats #1265
Conversation
@Bukhtawar may I ask you please to take a look, is it something you had mind or there are missing pieces? thank you! |
✅ DCO Check Passed 80afb4240ddc4d7330820b41c576b65cba628a55 |
✅ Gradle Wrapper Validation success 80afb4240ddc4d7330820b41c576b65cba628a55 |
✅ Gradle Precommit success 80afb4240ddc4d7330820b41c576b65cba628a55 |
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
start grade check |
@@ -299,7 +316,9 @@ public XContentBuilder toXContent(XContentBuilder builder, Params params) throws | |||
static final String PEAK_USED_IN_BYTES = "peak_used_in_bytes"; | |||
static final String PEAK_MAX = "peak_max"; | |||
static final String PEAK_MAX_IN_BYTES = "peak_max_in_bytes"; | |||
|
|||
static final String USAGE_PERCENT = "usage_percent"; |
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.
Can this be confused with current usage vs usage after GC?
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.
Good question, I think it should not since the field is under last_gc_stats
object, in this context, it should not be confusing. Also, the semantic of this field stays consistent between current usage (if we add it there) and usage after GC. What do you think?
❌ DCO Check Failed fd80400f525743b740268d4a1b1db6f6aa41374c |
✅ DCO Check Passed 2c362e40ab4ed1d3fa3af6b7fd00490fab337c1b |
✅ Gradle Wrapper Validation success 2c362e40ab4ed1d3fa3af6b7fd00490fab337c1b |
✅ Gradle Precommit success 2c362e40ab4ed1d3fa3af6b7fd00490fab337c1b |
@Bukhtawar anything pending for this change from your side? thank you! :-) |
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 @reta for the changes
@dblock may I ask you please to schedule Gradle check? Thank you! |
start gradle check |
❌ Gradle Check failure 2c362e40ab4ed1d3fa3af6b7fd00490fab337c1b |
Hm ...
Same as #1285 ? |
start gradle check |
Thanks for hanging in here! I kicked it, but I think this might need a rebase. |
❌ Gradle Check failure 2c362e40ab4ed1d3fa3af6b7fd00490fab337c1b |
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Rebased, thanks a lot @dblock ! |
✅ DCO Check Passed e7155ca |
✅ Gradle Wrapper Validation success e7155ca |
✅ Gradle Precommit success e7155ca |
start gradle check |
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
✅ DCO Check Passed 8dfe9a1 |
✅ Gradle Wrapper Validation success 8dfe9a1 |
start gradle check |
✅ Gradle Precommit success 8dfe9a1 |
Signed-off-by: Andriy Redko <andriy.redko@aiven.io>
Signed-off-by: Andriy Redko andriy.redko@aiven.io
Description
JVM stats published today represents the point in time usage of the heap across pools. While
MemoryPoolMXBean::getCollectionUsage
provides the memory usage after the Java virtual machine most recently expended effort in recycling unused objects in this memory pool. Exposing this information could be quite helpful while troubleshooting GC and memory issues.The
jvm
section of the node statistics had been extended to include the additional details regarding most recent GC cycle for a particular memory pool, under newlast_gc_stats
section:The sample output:
Issues Resolved
#981
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.