You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/10/10 10:07:00 UTC

[jira] [Closed] (FLINK-10243) Add option to reduce latency metrics granularity

     [ https://issues.apache.org/jira/browse/FLINK-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-10243.
------------------------------------
    Resolution: Fixed

1.6: 0600c17d18766c4ee985a1162a61623e044488e7
1.5: a5ee4ba09e4068b3207af4139f7c014411315741

> Add option to reduce latency metrics granularity
> ------------------------------------------------
>
>                 Key: FLINK-10243
>                 URL: https://issues.apache.org/jira/browse/FLINK-10243
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Configuration, Metrics
>    Affects Versions: 1.7.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> The latency is currently tracked separately from each operator subtask to each source subtask. The total number of latency metrics in the cluster is thus {{(# of sources) * (# of operators) * parallelism²}}, i.e. quadratic scaling.
> If we'd ignore the source subtask the scaling would be a lot more manageable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)