[
https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195554#comment-17195554
]
Piotr Nowojski edited comment on FLINK-17328 at 9/14/20, 4:08 PM:
------------------------------------------------------------------
Sorry [~chesnay], I think I've misunderstood you in that case.
Regarding the pool usages, they are helpful for two things:
# input pool usage is useful to find a task which is back-pressured but is not
back-pressuring upstream tasks. That's a temporary situation, but can happen.
Especially if task is emitting some large chunk of buffered data, like
{{WindowOperator}} after firing a timer.
# combination of average pool usage with "is back pressured" state, can be used
to distinguish between a case when a couple of channels are back-pressured
(data skew) or all of the channels are.
Both are not as important as the "is back-pressured" fact, but still useful and
hard to digest without the job graph (so Flink's UI is the only place that can
show them in an easy to understand way).
was (Author: pnowojski):
Sorry [~chesnay], I think I've misunderstood you in that case.
Regarding the pool usages, they are helpful for two things:
# input pool usage is useful to find a task which is back-pressured but is not
back-pressuring upstream tasks. That's a temporary situation, but can happen.
Especially if task is emitting some large chunk of buffered data, like
{{WindowOperator}} after firing a timer.
# combination of average pool usage with "is back pressured" state, can be used
to distinguish between a case when a couple of channels are back-pressured
(data skew) or all of the channels are.
Both are not as important as the "is back-pressured" fact, but still useful and
hard to digest without the job graph.
> Expose network metric for job vertex in rest api
> ------------------------------------------------
>
> Key: FLINK-17328
> URL: https://issues.apache.org/jira/browse/FLINK-17328
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics, Runtime / REST
> Reporter: lining
> Assignee: lining
> Priority: Major
> Labels: pull-request-available
>
> JobDetailsHandler
> * pool usage: outPoolUsageAvg, inputExclusiveBuffersUsageAvg,
> inputFloatingBuffersUsageAvg
> * back-pressured for show whether it is back pressured(merge all iths
> subtasks)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
