You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2018/09/13 09:16:00 UTC
[jira] [Updated] (FLINK-10331) Fix unnecessary flush requests to
the network stack
[ https://issues.apache.org/jira/browse/FLINK-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nico Kruber updated FLINK-10331:
--------------------------------
Description:
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.
was:
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 handled yet and 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.
> Fix unnecessary 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
>
> 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)