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

Posted to issues@flink.apache.org by "zlzhang0122 (Jira)" <ji...@apache.org> on 2020/10/30 06:30:00 UTC

[jira] [Closed] (FLINK-19876) Latency metrics can merge chain task latency metrics to reduce the number of latency metrics

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

zlzhang0122 closed FLINK-19876.
-------------------------------
    Resolution: Won't Fix

> Latency metrics  can merge chain task latency metrics to reduce the number of latency metrics
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLINK-19876
>                 URL: https://issues.apache.org/jira/browse/FLINK-19876
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>            Reporter: zlzhang0122
>            Priority: Major
>
> In latency metrics report, each operator will report themselves latency metics, but actually the communication between chain operators which in one task is very fast and the latency can be ignored.So maybe we can merge the chain operator latency metrics into one to decrease the number of it.
> For example, if source operator and downstream flat Map operator has been chained, now it will report the latency metrics separately, while we can merge it and make them report their latency metrics only once. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)