You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2020/04/23 14:59:00 UTC
[jira] [Commented] (FLINK-14815) Expose network metric for sub task
in rest api
[ https://issues.apache.org/jira/browse/FLINK-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090674#comment-17090674 ]
Piotr Nowojski commented on FLINK-14815:
----------------------------------------
[~lining], sorry I've missed the previous notification. Is this issue still valid?
> 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)