[
https://issues.apache.org/jira/browse/SAMZA-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979873#comment-14979873
]
Yi Pan (Data Infrastructure) commented on SAMZA-801:
----------------------------------------------------
Hi, [~theduderog], I was referring to something like
[this|http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fapi%2Forg%2Feclipse%2Fjface%2Futil%2FSafeRunnable.html].
I think that it is pretty much the same idea w/ yours. :)
> MetricsSnapshotReporter cannot tolerate errors
> -----------------------------------------------
>
> Key: SAMZA-801
> URL: https://issues.apache.org/jira/browse/SAMZA-801
> Project: Samza
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.9.1
> Reporter: Roger Hoover
>
> If an error occurs in MetricsSnapshotReporter.run(), it does not get logged
> anywhere and Executor.scheduleWithFixedDelay() will not reschedule it. The
> effect is that metrics stop being sent to the metrics topic.
> There should be a try/catch in MetricsSnapshotReporter.run() which logs
> errors and suppresses them to that the thread still had a chance to run again.
> I ran into this by creating a custom metric
> (https://github.com/Quantiply/rico/blob/master/core/src/main/java/com/quantiply/samza/metrics/WindowedMapGauge.java)
> that was accidentally unserializable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
