hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-910) Expose OMMetrics
Date Mon, 10 Dec 2018 09:50:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714500#comment-16714500
] 

Elek, Marton commented on HDDS-910:
-----------------------------------

Thanks [~bharatviswa] the patch. I have no problem with it, but can you please help me to
understand why is it required? I think the metrics worked without implementing MetricsSource
with all the other Ozone specific metrics class.

Did you use some specific MetricsSink?

Did you miss some metrics value from the JMX interface?

What was the original problem and how can I reproduce it?

(I am just curious and would like to learn more about the hadoop metrics...)

> Expose OMMetrics
> ----------------
>
>                 Key: HDDS-910
>                 URL: https://issues.apache.org/jira/browse/HDDS-910
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>         Attachments: HDDS-910.00.patch
>
>
> Implement MetricsSource interface, so that external metrics can collect the OMMetrics.
>  
> From *MetricsSource.java:*
> It registers with \{@link MetricsSystem}, which periodically polls it to collect \{@link
MetricsRecord} and passes it to \{@link MetricsSink}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message