[
https://issues.apache.org/jira/browse/RATIS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852774#comment-16852774
]
Tsz Wo Nicholas Sze commented on RATIS-574:
-------------------------------------------
Thanks [~swagle].
After the patch, there is no sleep between any retries for NotLeaderException.
The number of no-sleep-retries should be limited. Otherwise, the client will
be busy retrying if there is no leader (i.e. election is still ongoing.)
Ideally, the behavior should be a part of the retry policy. We may hardcode it
for now and make the retry policy change later.
> 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.02.patch,
> RATIS-574.03.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)
