You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2019/05/15 13:43:00 UTC
[jira] [Commented] (BEAM-6829) Duplicate metric warnings clutter
log
[ https://issues.apache.org/jira/browse/BEAM-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840405#comment-16840405 ]
Maximilian Michels commented on BEAM-6829:
------------------------------------------
This is due to an Executable Stage receiving metrics from multiple fused transforms. The current "legacy" metrics model assumes that we have an operator with a unique metrics namespace for each transform. I would suggest to use Flink's metric groups to add a sub group for every transform. Alternatively, we could include the transform name in the metric name.
> Duplicate metric warnings clutter log
> -------------------------------------
>
> Key: BEAM-6829
> URL: https://issues.apache.org/jira/browse/BEAM-6829
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.11.0
> Reporter: Thomas Weise
> Priority: Major
> Labels: portability
>
> Logs fill up quickly with these warnings:
> {code:java}
> WARN org.apache.flink.metrics.MetricGroup - Name collision: Group already contains a Metric with the name ...{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)