flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Nowojski (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FLINK-12576) inputQueueLength metric does not work for LocalInputChannels
Date Wed, 29 May 2019 13:26:01 GMT

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

Piotr Nowojski edited comment on FLINK-12576 at 5/29/19 1:25 PM:
-----------------------------------------------------------------

Yes, I think you are right. For example for {{PipelinedSubpartition}} this should return {{PipelinedSubpartition.buffers.size()}}


was (Author: pnowojski):
Yes, I think you are right. For example for \{{PipelinedSubpartition}} this should return
\{{PipelinedSubpartition.buffers.size()}}

> inputQueueLength metric does not work for LocalInputChannels
> ------------------------------------------------------------
>
>                 Key: FLINK-12576
>                 URL: https://issues.apache.org/jira/browse/FLINK-12576
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Metrics, Runtime / Network
>    Affects Versions: 1.6.4, 1.7.2, 1.8.0
>            Reporter: Piotr Nowojski
>            Assignee: aitozi
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently {{inputQueueLength}} ignores LocalInputChannels ({{SingleInputGate#getNumberOfQueuedBuffers}}).
This can can cause mistakes when looking for causes of back pressure (If task is back pressuring whole
Flink job, but there is a data skew and only local input channels are being used).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message