[
https://issues.apache.org/jira/browse/RATIS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015159#comment-17015159
]
Shashikant Banerjee commented on RATIS-777:
-------------------------------------------
[~ljain], If i remember correctly, the idea of AlreadyClosedException was to
first retry a request as per the retryPolicy configured and fail it with
RaftRetryPolicy and then fail all subsequent requests with
AlreadyClosedException thereby closing the raftClient. What is the need to
retry on AlreadyClosedException as it was explicitly added to not send any
other request using the same instance?
> Client should retry on AlreadyClosedException
> ---------------------------------------------
>
> Key: RATIS-777
> URL: https://issues.apache.org/jira/browse/RATIS-777
> Project: Ratis
> Issue Type: Bug
> Components: client
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Attachments: RATIS-777.001.patch
>
>
> RATIS-765 propagates AlreadyClosedException to client. Currently the client
> does not retry on receiving this exception leading to failure of request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
