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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/07/27 07:25:00 UTC

[jira] [Updated] (FLINK-18727) Remove the previous finished empty Buffer in PipelinedSubpartition when adding a new Buffer

     [ https://issues.apache.org/jira/browse/FLINK-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-18727:
-----------------------------------
    Labels: pull-request-available  (was: )

> Remove the previous finished empty Buffer in PipelinedSubpartition when adding a new Buffer
> -------------------------------------------------------------------------------------------
>
>                 Key: FLINK-18727
>                 URL: https://issues.apache.org/jira/browse/FLINK-18727
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Network
>            Reporter: Yingjie Cao
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> For current implementation of PipelinedSubpartition, empty Buffer consumes credit, which means we need at lease one credit to handle the finished empty Buffer without any data. We can remove and recycle the finished empty Buffer in the queue when adding a new Buffer, after which, the reader does not need any available credit to handle the finished empty buffer. For example, if the new buffer is an event and the previous buffer is finished but without any data, after it is removed, the reader is able to process the new added event without any available credit.



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