You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2019/06/05 03:32:01 UTC
[jira] [Updated] (RATIS-574) Client should not use configured sleep
interval in RetryPolicy when it gets NotLeaderException
[ https://issues.apache.org/jira/browse/RATIS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo Nicholas Sze updated RATIS-574:
--------------------------------------
Component/s: client
Issue Type: Improvement (was: Bug)
Summary: Client should not use configured sleep interval in RetryPolicy when it gets NotLeaderException (was: Ratis should not use configured sleep interval in RetryPolicy when it gets NotLeaderException)
> Client 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: Improvement
> Components: client
> Reporter: Aravindan Vijayan
> Assignee: Siddharth Wagle
> Priority: Major
> Attachments: RATIS-574.01.patch, RATIS-574.04.patch, RATIS-574.05.patch, RATIS-574.07.patch, RATIS-574.08.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)