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

Posted to issues@flink.apache.org by "Stefan Richter (JIRA)" <ji...@apache.org> on 2018/02/22 14:23:00 UTC

[jira] [Closed] (FLINK-8674) Efficiently handle alwaysFlush case (0ms flushTimeout)

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

Stefan Richter closed FLINK-8674.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Merged in a144d0f77f.

> Efficiently handle alwaysFlush case (0ms flushTimeout)
> ------------------------------------------------------
>
>                 Key: FLINK-8674
>                 URL: https://issues.apache.org/jira/browse/FLINK-8674
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Piotr Nowojski
>            Assignee: Piotr Nowojski
>            Priority: Major
>             Fix For: 1.5.0
>
>
> Changes in data notifications introduced alongside BufferConsumer significantly degraded performance of 0ms flushTimeout.
>  
> Previously flushing after writing only record, effectively triggered only one data notification for the sub-partition/channel to which this record was written. With low latency improvements, this changed and flush is now triggering data notifications for all of the partitions. This can (and should) be easily fixed.



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