[jira] [Updated] (RATIS-15) Add call ID to identify a client request and its retry

["Jing Zhao (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RATIS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jing Zhao updated RATIS-15:
---------------------------
    Attachment: RATIS-15.001.patch

Yes, actually for retry we do not need a long, int should be enough. But for RaftStream the seqNum may still needs to be a long to avoid overflow.

But on a second thought,  maybe we do not need to have two different types for this field. So the 001 patch always uses long, and rename most seqNum to callId (except for RaftOutputStream and AppendStreamer where "seqNum" makes more sense).

> Add call ID to identify a client request and its retry
> ------------------------------------------------------
>
>                 Key: RATIS-15
>                 URL: https://issues.apache.org/jira/browse/RATIS-15
>             Project: Ratis
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: RATIS-15.000.patch, RATIS-15.001.patch
>
>
> Add call ID in raft client. A client's request and its retry will share the same call ID. Remote Raft peers then can use "Client ID + Call ID" to identify the retry requests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)