[
https://issues.apache.org/jira/browse/RATIS-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059437#comment-18059437
]
Shilun Fan commented on RATIS-2413:
-----------------------------------
[~szetszwo] Thanks for raising this. I’ll submit a PR to address it and improve
the implementation.
> Support different RetryPolicy implementations
> ---------------------------------------------
>
> Key: RATIS-2413
> URL: https://issues.apache.org/jira/browse/RATIS-2413
> Project: Ratis
> Issue Type: Improvement
> Components: common
> Reporter: Tsz-wo Sze
> Priority: Major
>
> Currently, we have the following confs using RetryPolicy.
> - key: raft.server.log.appender.retry.policy (java.lang.String,
> ** default=1ms,10, 1s,20, 5s,1000):
> ** It must use MultipleLinearRandomRetry.
> - key: raft.netty.dataStream.client.reconnect.policy (java.lang.String,
> ** default=ExponentialBackoffRetry,100ms,5s,100)
> ** It must use ExponentialBackoffRetry.
> This JIRA is to make them supporting different RetryPolicy implementations.
> We may define a comma separated format for specifying a RetryPolicy
> - <classname>,<retry-policy-parameter>
> where <classname> is the class name of the RetryPolicy implementation and
> <retry-policy-parameter> is the parameters of that RetryPolicy in comma
> separated format.
> For compatibility with existing raft.server.log.appender.retry.policy,
> <classname> may be omitted and it will use MultipleLinearRandomRetry by
> default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
