[jira] [Closed] (FLINK-4054) Inconsistent Reporter synchronization within report()

["Chesnay Schepler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-4054.
-----------------------------------
    Resolution: Fixed

> Inconsistent Reporter synchronization within report()
> -----------------------------------------------------
>
>                 Key: FLINK-4054
>                 URL: https://issues.apache.org/jira/browse/FLINK-4054
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>    Affects Versions: 1.1.0
>            Reporter: Chesnay Schepler
>            Priority: Critical
>             Fix For: 1.1.0
>
>
> There are currently 2 distinct approaches to how added/removed metrics are handled while a Reporter is in report().
> The StatsDReporter simply catches possible exceptions (ConcurrentModificationException/NoSuchElementException) and reports the next time, while all other reporters access the metrics in a synchronized block.
> We should have a clear line as to which approach people should use.
> Whether FLINK-3998 is a valid issue depends on this decision.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)