[
https://issues.apache.org/jira/browse/RATIS-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated RATIS-90:
---------------------------
Attachment: RATIS-90.000.patch
Upload the patch to fix.
> After hitting IOException, RaftClient should randomly pick a known server as
> leader
> -----------------------------------------------------------------------------------
>
> Key: RATIS-90
> URL: https://issues.apache.org/jira/browse/RATIS-90
> Project: Ratis
> Issue Type: Bug
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: RATIS-90.000.patch
>
>
> This is an issue found by Nicholas: currently after the client hit an
> IOException when submitting request to a server (say s0 dies), it always pick
> the "next" raft server (say s1) in its local server list. If s1 returns a
> NotLeaderException and suggests s0 as the new leader, then the client may go
> into the same process again. We should let the client randomly pick a server
> from the list when it hits an exception and does not know which server is the
> new leader.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
