[
https://issues.apache.org/jira/browse/RATIS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017034#comment-17017034
]
Shashikant Banerjee commented on RATIS-777:
-------------------------------------------
Thanks [~ljain] for the explanation. As i mentioned before,
AlreadyClosedException is also generated on raftClient when we close the
raftClient instance and we should ideally not retry on client generated
exception. Its better to differentiate the clinet side and server side
exception for more clarity.
> 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)
