[
https://issues.apache.org/jira/browse/FLINK-12576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950674#comment-16950674
]
Jark Wu commented on FLINK-12576:
---------------------------------
Hi [~pnowojski], I was moving "OPEN" 1.9.0 issues to 1.9.2, because 1.9.0 has
already been released.
I didn't notice this is an "REOPEN" issue. So I reset it back to 1.9.0 now.
Btw, if the conclusion of the "REOPEN" issus is there are still something to
fix, then what the fixVersion should be?
Should we open another issue to track this?
> 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, 1.9.0
> Reporter: Piotr Nowojski
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.2
>
> Attachments: Screen Shot 2019-09-24 at 3.11.15 PM.png, Screen Shot
> 2019-09-24 at 3.13.05 PM.png, Screen Shot 2019-09-24 at 3.22.36 PM.png,
> Screen Shot 2019-09-24 at 3.22.53 PM.png,
> flink-1.8-2-single-slot-TMs-input.png,
> flink-1.8-2-single-slot-TMs-output.png, flink-1.8-input-subtasks.png,
> flink-1.8-output-subtasks.png, image-2019-09-26-11-34-24-878.png,
> image-2019-09-26-11-36-06-027.png
>
> Time Spent: 20m
> 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
(v8.3.4#803005)
