You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Arvid Heise (Jira)" <ji...@apache.org> on 2020/10/01 06:42:00 UTC

[jira] [Commented] (FLINK-16972) Fix non-blocking output availability logic.

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

Arvid Heise commented on FLINK-16972:
-------------------------------------

Merged into master as e17dbab24f4f71c5472d27267e938791686e45c3.

> Fix non-blocking output availability logic.
> -------------------------------------------
>
>                 Key: FLINK-16972
>                 URL: https://issues.apache.org/jira/browse/FLINK-16972
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Network
>    Affects Versions: 1.11.0
>            Reporter: Arvid Heise
>            Assignee: Arvid Heise
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> Non-blocking output is currently blocking, as unavailability in `LocalBufferPool` is only signaled when the first unavailable buffer is being requested.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)