[
https://issues.apache.org/jira/browse/RATIS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957094#comment-16957094
]
Mukul Kumar Singh commented on RATIS-727:
-----------------------------------------
[~szetszwo], the NLE retries are without timeout only for cases when the leader
is known, So if a NLE points to a peer being a leader, the next request is now
sent to the node which is the leader.
> 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)
