[jira] [Commented] (RATIS-574) Ratis should not use configured sleep interval in RetryPolicy when it gets NotLeaderException

["Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org>]

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

Tsz Wo Nicholas Sze commented on RATIS-574:
-------------------------------------------

Thanks [~swagle] for the update in https://github.com/apache/incubator-ratis/pull/22.  Some comments:
- Use retryForeverNoSleep() instead of retryUpToMaximumCountWithNoSleep(pending.getAttemptCount()) so that we don't have to change /RetryPolicies.java.
- Do not remove final from RaftClientReply.java 

Could you post the patch here so that Jenkins could test it?

> Ratis should not use configured sleep interval in RetryPolicy when it gets NotLeaderException
> ---------------------------------------------------------------------------------------------
>
>                 Key: RATIS-574
>                 URL: https://issues.apache.org/jira/browse/RATIS-574
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Aravindan Vijayan
>            Assignee: Siddharth Wagle
>            Priority: Major
>         Attachments: RATIS-574.01.patch, RATIS-574.04.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While doing performance tests with Ozone, it was observed that the client always waits for retry timeout when a NotLeaderException is logged. This bears a performance penalty for the client who cannot try the next Ratis server in the ring.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)