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

Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2023/10/14 01:50:00 UTC

[jira] [Commented] (RATIS-872) Ratis retry cache improvements

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

Tsz-wo Sze commented on RATIS-872:
----------------------------------

Failed RATIS-1903 and RATIS-1904 to do some code cleanup.

> Ratis retry cache improvements
> ------------------------------
>
>                 Key: RATIS-872
>                 URL: https://issues.apache.org/jira/browse/RATIS-872
>             Project: Ratis
>          Issue Type: Improvement
>          Components: client, server
>            Reporter: Lokesh Jain
>            Assignee: Tsz-wo Sze
>            Priority: Major
>         Attachments: Ratis Retry Cache Improvements.pdf
>
>
> The duration for which a client request entry is kept inside the retry cache should be long enough to cover all the retries made by the client. Retry cache would need to keep the metadata for all client requests until that duration is over. It can therefore require a large amount of heap in order to handle client requests. Since active heap usage is high it can also increase the frequency of JVM garbage collection.



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