flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10484) New latency tracking metrics format causes metrics cardinality explosion
Date Wed, 03 Oct 2018 11:41:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636838#comment-16636838
] 

Aljoscha Krettek commented on FLINK-10484:
------------------------------------------

Hi [~jgrier] :)

There is this issue and a bunch of other metrics-related issues that are being worked on for
1.7 (and also as bugfixes for earlier versions): FLINK-10246

> 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)

Mime
View raw message