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-7468) Implement sender backlog logic for credit-based
Date Wed, 29 Nov 2017 09:22:00 GMT

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

ASF GitHub Bot commented on FLINK-7468:

Github user NicoK commented on the issue:

    Regarding b): I just checked with #4552 and it looks as if the `backlog` is increased
from the `ResultWriter` / task thread, and then both read and decreased from netty's IO thread.
Therefore, we'll not only have a visibility problem here, but also a synchronisation problem
with the increment/decrement, won't we? 

> Implement sender backlog logic for credit-based
> -----------------------------------------------
>                 Key: FLINK-7468
>                 URL: https://issues.apache.org/jira/browse/FLINK-7468
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Network
>            Reporter: zhijiang
>            Assignee: zhijiang
>             Fix For: 1.5.0
> This is a part of work for credit-based network flow control.
> Receivers should know how many buffers are available on the sender side (the backlog).
The receivers use this information to decide how to distribute floating buffers.
> The {{ResultSubpartition}} maintains the backlog which only indicates the number of buffers
in this subpartition, not including the number of events. The backlog is increased for adding
buffer to this subpartition, and decreased for polling buffer from it.
> The backlog is attached in {{BufferResponse}} by sender as an absolute value after the
buffer being transferred.

This message was sent by Atlassian JIRA

View raw message