[
https://issues.apache.org/jira/browse/FLINK-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130157#comment-15130157
]
ASF GitHub Bot commented on FLINK-3310:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1578#issuecomment-179138699
Yes, it's independent and relevant for both streaming and batch.
I think you are raising a valid point with your last question. In contrast
to the other information in the web frontend, this one is more involved. We can
rename the tab to "Advanced" and then put back pressure statistics there (and
other advanced monitoring functionalities in the future). Do you like this
idea? Do you have any other ideas?
> Add back pressure statistics to web frontend
> --------------------------------------------
>
> Key: FLINK-3310
> URL: https://issues.apache.org/jira/browse/FLINK-3310
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Priority: Minor
>
> When a task is receiving data at a higher rate than it can process, the task
> is back pressuring preceding tasks. Currently, there is no way to tell
> whether this is the case or not. An indicator for back pressure is tasks
> being stuck in buffer requests on the network stack. This means that they
> have filled all their buffers with data, but the following tasks/network are
> not consuming them fast enough.
> A simple way to measure back pressure is to sample running tasks and report
> back pressure if they are stuck in the blocking buffers calls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
