[ https://issues.apache.org/jira/browse/RATIS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951512#comment-16951512 ]
Tsz-wo Sze commented on RATIS-704: ---------------------------------- > ... Currently the sliding window is reset at the creation of client and > whenever the client sees a NotLeader or IO exception. I guess we are not > addressing the second case. You are correct. Since it is hard to insert a dummy call in-between when there is an IOException, we will not include it in this simple work around. It is better to be fix it in the underlying RPC implementation. > Invoke sendAsync as soon as OrderedAsync is created > --------------------------------------------------- > > Key: RATIS-704 > URL: https://issues.apache.org/jira/browse/RATIS-704 > Project: Ratis > Issue Type: Improvement > Components: client > Reporter: Tsz-wo Sze > Assignee: Tsz-wo Sze > Priority: Major > Attachments: r704_20191009.patch, r704_20191011.patch > > > In OrderedAsync, the messages are sent asynchronously except for the first > message. The first message is used to establish the connection. > OrderedAsync will wait for the first message to complete before sending the > following messages. > Note that, when sending only two messages, the performance of sending the > messages asynchronously is degenerated to sending them sequentially > [~msingh] has discovered a case that can be optimized: an application may > send two or more messages and the first message may take a long time to > process. In this case, we may send a dummy lightweighted message establish > the connection, and then send real messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)