[
https://issues.apache.org/jira/browse/FLINK-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976456#comment-16976456
]
lining edited comment on FLINK-14814 at 11/18/19 11:20 AM:
-----------------------------------------------------------
We want to both.
1. present non aggregated metrics for subtask, it's to find which subtask is
blocked.
2. pool usage aggregated by max, min, and the average in every vertex for
users to judge vertex.
3. show FLINK-14813 back-pressured metric on vertex.
[~vthinkxie] , could you help us to review it.
was (Author: lining):
We want to both.
1. present non aggregated metrics for subtask, it's to find which subtask is
blocked.
2. pool usage aggregated by max, min, and the average in every vertex for users
to judge vertex.
3. show FLINK-14813 back-pressured metric on vertex.
Maybe [~vthinkxie] could help us to review it.
> 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)
