Group already contains a Metric with the name 'latency'

[rhashmi]

I am getting bunch of warning in log files. Anyone help me sort out this problem.


2017-04-28 00:20:57,947 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Timestamps/Watermarks, 4]
2017-04-28 00:20:57,955 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 4]
2017-04-28 00:20:57,962 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Timestamps/Watermarks, 1]
2017-04-28 00:20:57,968 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 1]
2017-04-28 00:20:57,968 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Timestamps/Watermarks, 7]
2017-04-28 00:20:57,976 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 7]
2017-04-28 00:20:57,969 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Timestamps/Watermarks, 10]
2017-04-28 00:20:57,978 WARN  org.apache.flink.metrics.MetricGroup                          - Name collision: Group already contains a Metric with the name 'latency'. Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager, c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 10]

[Chesnay Schepler]

Does your job include multiple operators called "Filter"?

On 16.05.2017 13:35, rizhashmi wrote:

> I am getting bunch of warning in log files. Anyone help me sort out this
> problem.
>
>
> 2017-04-28 00:20:57,947 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job,
> Timestamps/Watermarks, 4]
> 2017-04-28 00:20:57,955 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 4]
> 2017-04-28 00:20:57,962 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job,
> Timestamps/Watermarks, 1]
> 2017-04-28 00:20:57,968 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 1]
> 2017-04-28 00:20:57,968 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job,
> Timestamps/Watermarks, 7]
> 2017-04-28 00:20:57,976 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 7]
> 2017-04-28 00:20:57,969 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job,
> Timestamps/Watermarks, 10]
> 2017-04-28 00:20:57,978 WARN  org.apache.flink.metrics.MetricGroup
> - Name collision: Group already contains a Metric with the name 'latency'.
> Metric will not be reported.[vpc2w2-rep-stage-flink2, taskmanager,
> c5c676c57eca2c127ba1243394658e8a, Flink Streaming Job, Filter, 10]
>
>
>
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Group-already-contains-a-Metric-with-the-name-latency-tp13157.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
>

[rhashmi]

In my implementation i am generating rollup for multiple timezone. So i took path of creating windows per timezone,  for each window separate instance of trigger created window with a new instance AssignerWithPunctuatedWatermarks & each time i applied same filter.

Does this imply issue?

[Chesnay Schepler]

Generally this isn't an issue; it only means that for some operators the
latency metrics will not be available. The underlying issue is that the
metric system has no way to differentiate operators except by their
name; if the names are identical you end up with a collision.

If you're not using the latency metrics there's nothing to worry about.
To prevent this warning from occurring you will have to give every
operator a unique name.

On 16.05.2017 14:17, rizhashmi wrote:

>   i think i do have.
>
> In my implementation i am generating rollup for multiple timezone. So i took
> path of creating windows per timezone,  for each window separate instance of
> trigger created window with a new instance AssignerWithPunctuatedWatermarks
> & each time i applied same filter.
>
> Does this imply issue?
>
>
>
>
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Group-already-contains-a-Metric-with-the-name-latency-tp13157p13161.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
>

[rhashmi]

thanks for your reply

latency metrics appear to be pushed by AbstractStreamOperator.java

latencyGauge = this.metrics.gauge("latency", new LatencyGauge(historySize));

does it mean this methods need to be override?

[Chesnay Schepler]

No; you can name operators like this:

stream.map(<mapFunction>).name("MyUniqueMapFunctionName")

On 16.05.2017 14:50, rizhashmi wrote:

> thanks for your reply
>
> *latency* metrics appear to be pushed by AbstractStreamOperator.java
>
> latencyGauge = this.metrics.gauge("latency", new LatencyGauge(historySize));
>
> does it mean this methods need to be override?
>
>
>
>
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Group-already-contains-a-Metric-with-the-name-latency-tp13157p13164.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
>

[rhashmi]

thanks Chesnay Schepler