[
https://issues.apache.org/jira/browse/FLINK-30829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682399#comment-17682399
]
Yun Tang commented on FLINK-30829:
----------------------------------
[~Zhanghao Chen] What do you mean "backpressure level", do you mean the
"Backpressure Status" tab? We use the newly added busy metrics to find which
subtask is the bottleneck, and the previous existing "Backpressure Status" tab
is used to find which subtask is mostly backpressured but cannot find which
subtask is the bottleneck in the downstream side.
>From my point of view, since we already introduced the busy tab, which makes
>sorting by backpressured status a bit meaningless.
> Make the backpressure tab could be sort by the backpressure level
> -----------------------------------------------------------------
>
> Key: FLINK-30829
> URL: https://issues.apache.org/jira/browse/FLINK-30829
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Affects Versions: 1.17
> Reporter: Zhanghao Chen
> Priority: Major
>
> [FLINK-29998|https://issues.apache.org/jira/browse/FLINK-29998] enables user
> to sort the backpressure tab to see which task is busiest. Another common
> scenario for backpressure analysis is to find which tasks are backpressured.
> We should add support to sort the backpressure tab by backpressure level as
> well.
>
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
