[
https://issues.apache.org/jira/browse/RATIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082263#comment-17082263
]
Lokesh Jain commented on RATIS-835:
-----------------------------------
[~shashikant] Thanks for reviewing the patch! That would be good to have. There
is a single instance of retryPolicy used by all the client requests.
RetryPolicy would have to maintain the metadata for all the client requests and
we will need to add logic to clear the metadata for every request as well.
Clearing the metadata in a retry policy would require separate calls and would
not make sense.
Client can benefit from this info as we can populate it in metrics.
> Include exception based attempt count in raft client request
> ------------------------------------------------------------
>
> Key: RATIS-835
> URL: https://issues.apache.org/jira/browse/RATIS-835
> Project: Ratis
> Issue Type: Bug
> Components: client
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Attachments: RATIS-835.001.patch, RATIS-835.002.patch,
> RATIS-835.003.patch
>
>
> Client needs to maintain exception based attempt count for using Exception
> Dependent retry policy. Exception dependent policy helps in specifying
> individual policies for different exception types.
> Currently policy takes number of attempts as argument. Therefore the
> individual policies require attempt counts for the particular exception while
> handling retry event. This is particularly important for using
> MulipleLinearRandomRetry policy which increases sleep interval based on
> number of attempts made by the client. Raft Client can therefore use this
> policy for ResourceUnavailableException and increase sleep interval for
> subsequent retries of the request on the same exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
