[
https://issues.apache.org/jira/browse/FLINK-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277052#comment-16277052
]
ASF GitHub Bot commented on FLINK-7416:
---------------------------------------
Github user pnowojski commented on a diff in the pull request:
https://github.com/apache/flink/pull/4533#discussion_r154702193
--- Diff:
flink-runtime/src/test/java/org/apache/flink/runtime/io/network/netty/PartitionRequestClientHandlerTest.java
---
@@ -244,54 +237,89 @@ public void testCancelBeforeActive() throws Exception
{
}
/**
- * Verifies that {@link RemoteInputChannel} is enqueued in the
pipeline, and
- * {@link AddCredit} message is sent to the producer.
+ * Verifies that {@link RemoteInputChannel} is enqueued in the pipeline
for notifying credits,
+ * and verifies the behaviour of credit notification by triggering
channel's writability changed.
*/
@Test
public void testNotifyCreditAvailable() throws Exception {
+ final SingleInputGate inputGate = createSingleInputGate();
+ final RemoteInputChannel inputChannel1 =
spy(createRemoteInputChannel(inputGate));
+ final RemoteInputChannel inputChannel2 =
spy(createRemoteInputChannel(inputGate));
final CreditBasedClientHandler handler = new
CreditBasedClientHandler();
- final EmbeddedChannel channel = new EmbeddedChannel(handler);
+ final EmbeddedChannel channel = spy(new
EmbeddedChannel(handler));
--- End diff --
I think this `spy` is not needed anywhere?
> 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.5.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)
