[
https://issues.apache.org/jira/browse/FLINK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353280#comment-15353280
]
ASF GitHub Bot commented on FLINK-1550:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2146
I moved the checkpoint metrics into the Tracker (and reverted the changed
to ExecutionGraph). Currently trying it out locally.
Regarding the exception catching in the metrics: I can't decide whether we
should try to write all metrics in such a way that they can't throw exceptions,
or write the reporters in such a way that they can deal with it. (usually by
logging the exception). The first option is safer considering custom reporters,
but the second will allows us to properly log them.
Regarding a test: While i agree that such a test would be nice i can only
come up with icky ways to test it. You have to access the metric _while a job
is running_ as they are removed afterwards. So you either have to submit a job
that blocks until _something_ happens, or you add a reporter that feeds that
information back to the test _somehow_.
> Show JVM Metrics for JobManager
> -------------------------------
>
> Key: FLINK-1550
> URL: https://issues.apache.org/jira/browse/FLINK-1550
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager, Metrics
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
> Fix For: pre-apache
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
