[
https://issues.apache.org/jira/browse/FLINK-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637877#comment-16637877
]
Chesnay Schepler commented on FLINK-10484:
------------------------------------------
It shouldn't be that difficult to backport. We could also backport
https://issues.apache.org/jira/browse/FLINK-10242 which adds a configuration
option to set the default latency tracking interval, so you could disable
latency metrics unless the application opts in.
> New latency tracking metrics format causes metrics cardinality explosion
> ------------------------------------------------------------------------
>
> Key: FLINK-10484
> URL: https://issues.apache.org/jira/browse/FLINK-10484
> Project: Flink
> Issue Type: Bug
> Components: Metrics
> Affects Versions: 1.6.0, 1.6.1, 1.5.4
> Reporter: Jamie Grier
> Assignee: Jamie Grier
> Priority: Critical
>
> The new metrics format for latency tracking causes huge metrics cardinality
> explosion due to the format and the fact that there is a metric reported for
> a every combination of source subtask index and operator subtask index.
> Yikes!
> This format is actually responsible for basically taking down our metrics
> system due to DDOSing our metrics servers (at Lyft).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
