You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lining (Jira)" <ji...@apache.org> on 2019/11/18 02:58:00 UTC

[jira] [Comment Edited] (FLINK-14814) Show the vertex that produces the backpressure source in the job

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

lining edited comment on FLINK-14814 at 11/18/19 2:57 AM:
----------------------------------------------------------

Now we may just show this information in the Web Frontend. I add a screenshot for it.
 But there's one problem:
      _Supplement another case for invalid judging via outputUsage. If there are two output edges, the current metric of outputUsage calculates them together. That means if one output usage is already 100% and the other output is not, then the outputUsage you see would be less that 100%. But in this case it is actually back pressured_. from [~zjwang] 
 Above all, we could depend on not only pool usage, but also the back-pressured metric from FLINK-14813. If the back-pressured metric shows no, we could show pool usage for the user to real-time monitor.


was (Author: lining):
Now we may just show this information in the Web Frontend. I add a screenshot for it.
But there's one problem:
     _Supplement another case for invalid judging via outputUsage. If there are two output edges, the current metric of outputUsage calculates them together. That means if one output usage is already 100% and the other output is not, then the outputUsage you see would be less that 100%. But in this case it is actually back pressured_. - from [~zjwang] 
Above all, we could depend on not only pool usage, but also the back-pressured metric from FLINK-14813. If the back-pressured metric shows no, we could show pool usage for the user to real-time monitor.

> Show the vertex that produces the backpressure source in the job
> ----------------------------------------------------------------
>
>                 Key: FLINK-14814
>                 URL: https://issues.apache.org/jira/browse/FLINK-14814
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Metrics, Runtime / Network, Runtime / REST, Runtime / Web Frontend
>            Reporter: lining
>            Assignee: lining
>            Priority: Major
>         Attachments: 2B0E910D-6D95-401F-B450-1F6B1AFB9BEA.png
>
>
> By checking the status of output and input buffer pools exposed via FLINK-14815 (output buffer empty, input buffer full) it is possible to display which node is a source of the back pressure. This information could be displayed/accessible in the Web Frontend.



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