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

Chesnay Schepler closed FLINK-9789.
-----------------------------------

master: 60df251ad34ac033ed6c4423a69765739cb04199
1.5: a0a810720d251fb9ab6a4cf9d995828d99a3f2c8

> Watermark metrics for an operator&task shadow each other
> --------------------------------------------------------
>
>                 Key: FLINK-9789
>                 URL: https://issues.apache.org/jira/browse/FLINK-9789
>             Project: Flink
>          Issue Type: Bug
>          Components: Metrics
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.5.1, 1.6.0
>
>
> In FLINK-4812 we reworked the watermark metrics to be exposed for each 
> operator.
> In FLINK-9467 we made further modifications to also expose these metrics 
> again for tasks.
> In both JIRAs we register a single metric multiple times, for example the 
> input watermark metric is registered for both the first operator in the task, 
> and the task itself.
> Unfortunately, the metric system assumes metric objects to be unique, as can 
> be seen in virtually all reporter implementations as well as the 
> MetricQueryService.
> As a result the watermark metrics override each other in the reporter, 
> causing only one to be reported, whichever was registered last.



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

Reply via email to