[
https://issues.apache.org/jira/browse/FLINK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhijiang updated FLINK-7416:
----------------------------
Description:
This is a part of work for credit-based network flow control.
The related works are :
* We define a new message called {{AddCredit}} to notify the incremental
credit during data shuffle.
* Whenever an {{InputChannel}}’s unannounced credit goes up from zero, the
channel is enqueued in the pipeline.
* Whenever the channel becomes writable, it takes the next {{InputChannel}} and
sends its unannounced credit. The credit is reset to zero after each sent.
* That way, messages are sent as often as the network has capacity and contain
as much credit as available for the channel at that point in time. Otherwise,
it would only add latency to the announcements and not increase throughput.
was:
This is a part of work for credit-based network flow control.
The related works are :
* The {{InputChannel}} notifies the initial credit which equals to the number
of exclusive buffers per channel via {{PartitionRequest}} message.
* We define another message called {{AddCredit}} to notify the incremental
credit during data shuffle.
* Whenever an {{InputChannel}}’s unannounced credit goes up from zero, the
channel is enqueued in the pipeline.
* Whenever the channel becomes writable, it takes the next {{InputChannel}} and
sends its unannounced credit. The credit is reset to zero after each sent.
* That way, messages are sent as often as the network has capacity and contain
as much credit as available for the channel at that point in time. Otherwise,
it would only add latency to the announcements and not increase throughput.
> Implement Netty receiver outgoing pipeline for credit-based
> -----------------------------------------------------------
>
> Key: FLINK-7416
> URL: https://issues.apache.org/jira/browse/FLINK-7416
> Project: Flink
> Issue Type: Sub-task
> Components: Network
> Reporter: zhijiang
> Assignee: zhijiang
> Fix For: 1.4.0
>
>
> This is a part of work for credit-based network flow control.
> The related works are :
> * We define a new message called {{AddCredit}} to notify the incremental
> credit during data shuffle.
> * Whenever an {{InputChannel}}’s unannounced credit goes up from zero, the
> channel is enqueued in the pipeline.
> * Whenever the channel becomes writable, it takes the next {{InputChannel}}
> and sends its unannounced credit. The credit is reset to zero after each sent.
> * That way, messages are sent as often as the network has capacity and
> contain as much credit as available for the channel at that point in time.
> Otherwise, it would only add latency to the announcements and not increase
> throughput.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
