You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Anu Engineer (JIRA)" <ji...@apache.org> on 2019/07/22 23:50:00 UTC
[jira] [Updated] (HDDS-1710) Publish JVM metrics via Hadoop metrics
[ https://issues.apache.org/jira/browse/HDDS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anu Engineer updated HDDS-1710:
-------------------------------
Resolution: Fixed
Fix Version/s: 0.4.1
0.5.0
Status: Resolved (was: Patch Available)
Thank you for your contribution. I have committed this patch to trunk and ozone-0.4.1
> Publish JVM metrics via Hadoop metrics
> --------------------------------------
>
> Key: HDDS-1710
> URL: https://issues.apache.org/jira/browse/HDDS-1710
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: om, Ozone Datanode, SCM
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0, 0.4.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> In ozone metrics can be published with the help of hadoop metrics (for example via PrometheusMetricsSink)
> The basic jvm metrics are not published by the metrics system (just with JMX)
> I am very interested about the basic JVM metrics (gc count, heap memory usage) to identify possible problems in the test environment.
> Fortunately it's very easy to turn it on with the help of org.apache.hadoop.metrics2.source.JvmMetrics.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org