[ https://issues.apache.org/jira/browse/FLINK-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638756#comment-16638756 ]
Jamie Grier edited comment on FLINK-10484 at 10/4/18 7:46 PM: -------------------------------------------------------------- Cool. We should definitely backport FLINK-10242 as well then. Are you going to do this [~Zentol] or should I take a crack at it ? was (Author: jgrier): Cool. We should definitely backport [FLINK-10242] as well then. Would you like to do this [~Zentol] or should I do it? > 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)