You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2016/06/10 13:08:21 UTC
[jira] [Closed] (FLINK-3998) Access to gauges and counters in
StatsDReporter#report() is not properly synchronized
[ https://issues.apache.org/jira/browse/FLINK-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-3998.
-----------------------------------
Resolution: Not A Problem
Exceptions caused by missing synchronization are catched, and the reporting delayed to the next round.
This case can only occur on startup/teardown of the job/task/operator. During this period, synchronization may produce additional overhead that should be avoided.
> Access to gauges and counters in StatsDReporter#report() is not properly synchronized
> -------------------------------------------------------------------------------------
>
> Key: FLINK-3998
> URL: https://issues.apache.org/jira/browse/FLINK-3998
> Project: Flink
> Issue Type: Bug
> Reporter: Ted Yu
>
> {code}
> for (Map.Entry<Gauge<?>, String> entry : gauges.entrySet()) {
> reportGauge(entry.getValue(), entry.getKey());
> }
> for (Map.Entry<Counter, String> entry : counters.entrySet()) {
> reportCounter(entry.getValue(), entry.getKey());
> {code}
> Access to gauges and counters should be protected by lock on AbstractReporter.this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)