You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/10/17 08:40:00 UTC

[jira] [Updated] (FLINK-10331) Reduce number of flush requests to the network stack

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

Chesnay Schepler updated FLINK-10331:
-------------------------------------
    Summary: Reduce number of flush requests to the network stack  (was: Fix unnecessary flush requests to the network stack)

> Reduce number of flush requests to the network stack
> ----------------------------------------------------
>
>                 Key: FLINK-10331
>                 URL: https://issues.apache.org/jira/browse/FLINK-10331
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Network
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.7.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.5, 1.6.2, 1.7.0
>
>
> With the re-design of the record writer interaction with the result(sub)partitions, flush requests can currently pile up in these scenarios:
> - a previous flush request has not been completely handled yet and/or is still enqueued or
> - the network stack is still polling from this subpartition and doesn't need a new notification
> These lead to increased notifications in low latency settings (low output flusher intervals) which can be avoided.



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