[
https://issues.apache.org/jira/browse/RATIS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765740#comment-17765740
]
Tsz-wo Sze commented on RATIS-872:
----------------------------------
Quoted from
https://issues.apache.org/jira/secure/attachment/13000693/Ratis%20Retry%20Cache%20Improvements.pdf
bq. Currently the ratis server is not informed about the last seen callId by
the ratis client. ...
That is a good point! Clients should inform the server the last seen call id.
Then, the server could drop the cached entries.
> Ratis retry cache improvements
> ------------------------------
>
> Key: RATIS-872
> URL: https://issues.apache.org/jira/browse/RATIS-872
> Project: Ratis
> Issue Type: Bug
> Components: client, server
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> 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)
