[
https://issues.apache.org/jira/browse/RATIS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957123#comment-16957123
]
Tsz-wo Sze commented on RATIS-727:
----------------------------------
[~msingh], if it is the case, then it may be related the configured retry
policy.
Anyway, if the 7 requests were sent according to the retry policy to check
whether the server becomes a leader, it does not sound like a bug. We could
have some improvement such as RATIS-704 or the real fix in the RPC
implementation.
> Garbage collection due to same request retries on a follower
> ------------------------------------------------------------
>
> Key: RATIS-727
> URL: https://issues.apache.org/jira/browse/RATIS-727
> Project: Ratis
> Issue Type: Bug
> Components: client
> Reporter: Lokesh Jain
> Priority: Major
>
> In a heap dump it could be seen that a client request retries on the same
> follower multiple times and every time the request is rejected with a
> NotLeaderException. In case of Ozone it is a WriteChunk request which leads
> to garbage collection of 16MB for every request. In the heap dump a client
> request retries multiple times leading to garbage collection of ~100MB.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
