[
https://issues.apache.org/jira/browse/HDDS-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891261#comment-16891261
]
Hudson commented on HDDS-1710:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16974 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16974/])
HDDS-1710. Fix checkstyle errors (aengineer: rev
278390f5bf9287dd9e91d0fb9a600618eaecd2b9)
* (edit)
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/StorageContainerManager.java
* (edit)
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
* (edit) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/HddsUtils.java
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/HddsDatanodeService.java
> 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: 2h 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: [email protected]
For additional commands, e-mail: [email protected]
