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

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

Github user zhijiangW commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4533#discussion_r145746120
  
    --- Diff: 
flink-runtime/src/test/java/org/apache/flink/runtime/io/network/partition/consumer/RemoteInputChannelTest.java
 ---
    @@ -304,12 +304,21 @@ public void testProducerFailedException() throws 
Exception {
     
        /**
         * Tests {@link RemoteInputChannel#recycle(MemorySegment)}, verifying 
the exclusive segment is
    -    * recycled to available buffers directly and it triggers notify of 
announced credit.
    +    * recycled to available buffers directly and it triggers notification 
of unannounced credit.
         */
        @Test
        public void testRecycleExclusiveBufferBeforeReleased() throws Exception 
{
    +           // Config
    +           final Tuple2<Integer, Integer> backoff = new Tuple2<>(0, 0);
    +
    +           // Setup
    +           final PartitionRequestClient connClient = 
mock(PartitionRequestClient.class);
                final SingleInputGate inputGate = mock(SingleInputGate.class);
    -           final RemoteInputChannel inputChannel = 
spy(createRemoteInputChannel(inputGate));
    +
    +           RemoteInputChannel inputChannel = 
spy(createRemoteInputChannel(inputGate, connClient, backoff));
    --- End diff --
    
    Your code may be out of date. The current code has not this issue.


> 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)

Reply via email to