[
https://issues.apache.org/jira/browse/FLINK-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195452#comment-17195452
]
Piotr Nowojski commented on FLINK-14815:
----------------------------------------
Thanks for the confirmation [~lining]. What should I take a look at? I think in
the last two comments in this issue from November, we reached the consensus
that:
* we would present if task is backpressured based on {{isBackPressured}} metric
(the red mark over a task)
* for aggregation we would provide {{average}} over buffer pools usage (could
also be displayed on the job graph?)
> Expose network metric for sub task in rest api
> ----------------------------------------------
>
> Key: FLINK-14815
> URL: https://issues.apache.org/jira/browse/FLINK-14815
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics, Runtime / Network, Runtime / REST
> Reporter: lining
> Assignee: lining
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * SubTask
> ** pool usage: outPoolUsage, inputExclusiveBuffersUsage,
> inputFloatingBuffersUsage.
> *** If the subtask is not back pressured, but it is causing backpressure
> (full input, empty output)
> *** By comparing exclusive/floating buffers usage, whether all channels are
> back-pressure or only some of them
> ** back-pressured for show whether it is back pressured.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
