You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "yuuka (Jira)" <ji...@apache.org> on 2024/09/30 10:00:00 UTC

[jira] [Commented] (RATIS-2165) Discussion on canceling transmission of RaftClientRequest. Message in RaftServerImpl.sendReadIndexAsync to further optimize transmission efficiency

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

yuuka commented on RATIS-2165:
------------------------------

Ok! I will submit a pr for this issue

> Discussion on canceling transmission of RaftClientRequest. Message in RaftServerImpl.sendReadIndexAsync to further optimize transmission efficiency
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RATIS-2165
>                 URL: https://issues.apache.org/jira/browse/RATIS-2165
>             Project: Ratis
>          Issue Type: Improvement
>          Components: Linearizable Read
>            Reporter: yuuka
>            Priority: Major
>         Attachments: image-2024-09-27-10-30-12-499.png, image-2024-09-27-10-31-07-635.png, image-2024-09-27-10-31-17-774.png, image-2024-09-27-10-31-21-531.png
>
>
> It seems that in RaftServerImpl.sendReadIndexAsync, we do not need to serialize the message of the request, because we only use request.getClientId ().
> !image-2024-09-27-10-31-17-774.png!
> !image-2024-09-27-10-31-21-531.png!
> For this situation, we can provide a setMessage interface that is set to null every time sendReadAsync is called.
> Or we can regenerate a RaftClientRequest without Message.
>  
> Whether this has good returns can be further discussed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)