flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3310) Add back pressure statistics to web frontend
Date Thu, 04 Feb 2016 10:43:39 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132123#comment-15132123

ASF GitHub Bot commented on FLINK-3310:

Github user uce commented on the pull request:

    It's definitely a good thing in my opinion. I was just asking whether we should "hide"
it behind an Advanced tab (with further advanced monitoring features in the future).

> 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

View raw message