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

["Siddharth Wagle (JIRA)" <ji...@apache.org>]

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

Siddharth Wagle edited comment on RATIS-574 at 5/31/19 8:36 PM:
----------------------------------------------------------------

Thanks for the review [~szetszwo], I updated the *pull request* to retry with no sleep only if there is a suggested leader. So if there is no leader elected we fallback to the same behavior as before. I am opening a sperate Jira to address refactor RetryPolicy based on Exception.


was (Author: swagle):
Thanks for the review [~szetszwo], I updated the pull request to retry with no sleep only is there is a suggested leader. So if there is no leader elected we fallback to the same behavior as before. I am opening a sperate Jira to address refactor RetryPolicy based on Exception.

> 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)