You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/01/15 11:55:39 UTC

[jira] [Resolved] (FLINK-3232) Add option to eagerly deploy channels

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

Stephan Ewen resolved FLINK-3232.
---------------------------------
    Resolution: Fixed

Fixed via 0937be0a94eae0b47f0a5f0206e62a98bcbc8432

> Add option to eagerly deploy channels
> -------------------------------------
>
>                 Key: FLINK-3232
>                 URL: https://issues.apache.org/jira/browse/FLINK-3232
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Runtime
>    Affects Versions: 0.10.1
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> Intermediate partitions are consumed via input channels. These channels are instantiated lazily when the partition producer emits the first record. This can lead to higher latencies for the first records passing the pipeline.
> In order to decrease this latency, we can deploy channels eagerly.
> I would like to add this as a flag to the intermediate results of the execution graph. On deployment, the task can then deploy the input channels as soon as the intermediate stream has been registered at the partition manager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)