[
https://issues.apache.org/jira/browse/RATIS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo Nicholas Sze updated RATIS-453:
--------------------------------------
Description: Suppose client has made more than one async calls and then
waits for the replies. Suppose the leader is not ready or some other transient
problem. The retries on the first async call may fail, the code will set
RaftRetryFailureException in the reply. However, the retries of the following
async calls may succeed. In such case, the call ordering is not guaranteed --
a later call succeeds without delivered an earlier call. (was: Suppose client
has made more than one async calls and then waits for the replies. Suppose the
leader is not ready. The retries on the first async call may fail, the code
will set RaftRetryFailureException in the reply. However, the retries of the
following async calls may succeed. In such case, the call ordering is not
guaranteed.)
> When retry failed on an async call, it should fails all the following calls
> in the sliding window
> -------------------------------------------------------------------------------------------------
>
> Key: RATIS-453
> URL: https://issues.apache.org/jira/browse/RATIS-453
> Project: Ratis
> Issue Type: Bug
> Components: client
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
>
> Suppose client has made more than one async calls and then waits for the
> replies. Suppose the leader is not ready or some other transient problem.
> The retries on the first async call may fail, the code will set
> RaftRetryFailureException in the reply. However, the retries of the
> following async calls may succeed. In such case, the call ordering is not
> guaranteed -- a later call succeeds without delivered an earlier call.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
