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-8523) Stop assigning floating buffers for blocked input channels in exactly-once mode
Date Tue, 30 Jan 2018 08:22:00 GMT

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

ASF GitHub Bot commented on FLINK-8523:
---------------------------------------

Github user zhijiangW commented on the issue:

    https://github.com/apache/flink/pull/5381
  
    @pnowojski I have submitted the whole process in one commit.
    
    After you verify the implementation is feasible, I will submit a separate commit for adding
unit tests based on this process.


> Stop assigning floating buffers for blocked input channels in exactly-once mode
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-8523
>                 URL: https://issues.apache.org/jira/browse/FLINK-8523
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Network
>    Affects Versions: 1.5.0
>            Reporter: zhijiang
>            Assignee: zhijiang
>            Priority: Major
>
> In exactly-once mode, the input channel is set blocked state when reading barrier from
it. And the blocked state will be released after barrier alignment or cancelled.
>  
> In credit-based network flow control, we should avoid assigning floating buffers for
blocked input channels because the buffers after barrier will not be processed by operator
until alignment.
> To do so, we can fully make use of floating buffers and speed up barrier alignment in
some extent.



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

Mime
View raw message