flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3232) Add option to eagerly deploy channels
Date Thu, 14 Jan 2016 20:52:39 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098829#comment-15098829

ASF GitHub Bot commented on FLINK-3232:

Github user StephanEwen commented on the pull request:

    Good fix, +1
    Will merge this...

> 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

View raw message