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

Posted to dev@flink.apache.org by "Jozef Vilcek (JIRA)" <ji...@apache.org> on 2018/08/27 12:35:00 UTC

[jira] [Created] (FLINK-10226) Latency metrics can choke job-manager

Jozef Vilcek created FLINK-10226:
------------------------------------

             Summary: Latency metrics can choke job-manager
                 Key: FLINK-10226
                 URL: https://issues.apache.org/jira/browse/FLINK-10226
             Project: Flink
          Issue Type: Improvement
    Affects Versions: 1.5.0
            Reporter: Jozef Vilcek


With Flink 1.5.0 my Apache Beam job was not runnable unless I turned off latencyTracking feature. That job generated huge amount of latency metrics + histogram aggregates which updating occupied job-manager too much and cluster did fall appart.

This was discussed on mailing list:

[http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Flink-cluster-crashing-going-from-1-4-0-gt-1-5-3-td23941.html]

The purpose of the ticket is reason about how to improve this and on which end. I am currently not sure what is the root cause:
a) Beam-To-Flink translation does generate too much of of "noise operators"
b) Flink does not handle latencyTracking well for large jobs 

 



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