You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2019/05/30 05:01:00 UTC

[jira] [Comment Edited] (RATIS-574) Ratis should not use configured sleep interval in RetryPolicy when it gets LeaderNotException without an actual Leader election going on

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

Siddharth Wagle edited comment on RATIS-574 at 5/30/19 5:00 AM:
----------------------------------------------------------------

Added a unit test which exactly reproduces the exception. The fix is for the retry policy to not honor the timeout if NotLeaderException.


was (Author: swagle):
Added a unit test which exactly reproduces the exception. The fix is for the retry policy to not honor the timeout.

> Ratis should not use configured sleep interval in RetryPolicy when it gets LeaderNotException without an actual Leader election going on
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 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
>
>
> 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)