[
https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated RATIS-709:
--------------------------------------
Description: Currently, when a watch request times out with a
NotReplicatedException on the leader raft client starts retrying the request on
different server and starts failing with NotLeaderException and it goes in a
loop. Ideally , when a watch request times out , it should not be retried
automatically by raft client. (was: Currently, when a watch request times out
with a NotReplicatedException on the leader raft client starts retrying the
request on different server and starts failing with NotLeaderException and it
goes in a loop. Ideally , when a watch request times out , it should be retried
automatically by raft client.)
> RaftClient should not retry on a different leader on NotReplicated exception
> from leader
> ----------------------------------------------------------------------------------------
>
> Key: RATIS-709
> URL: https://issues.apache.org/jira/browse/RATIS-709
> Project: Ratis
> Issue Type: Bug
> Components: client
> Reporter: Shashikant Banerjee
> Assignee: Sammi Chen
> Priority: Major
> Fix For: 0.5.0
>
>
> Currently, when a watch request times out with a NotReplicatedException on
> the leader raft client starts retrying the request on different server and
> starts failing with NotLeaderException and it goes in a loop. Ideally , when
> a watch request times out , it should not be retried automatically by raft
> client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
