[jira] [Commented] (RATIS-153) asyncAppendEntries misses updating followerstate at end of logsync

["Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RATIS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333828#comment-16333828 ] 

Tsz Wo Nicholas Sze commented on RATIS-153:
-------------------------------------------

Thanks Mukul and Lokesh.  I don't have any other comments on the patch.

> asyncAppendEntries misses updating followerstate at end of logsync
> ------------------------------------------------------------------
>
>                 Key: RATIS-153
>                 URL: https://issues.apache.org/jira/browse/RATIS-153
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Mukul Kumar Singh
>            Assignee: Mukul Kumar Singh
>            Priority: Major
>         Attachments: RATIS-153.001.patch
>
>
> Currently the heartbeat monitor on the follower is updated when the last rpc is received from the leader. When this threshold crosses the *raft.server.rpc.timeout*, an election is triggered to elect a new leader.
> However generally it might happen that the leader doesn't had append entries to forward to the follower. This will trigger unnecessary leader elections.
> This also causes the Raft Client to find the new Leader as well which can be time consuming.
> This jira proposes to add a heartbeat mechanism, where the leader will periodically (lets say, raft.server.rpc.timeout/2) will send empty heartbeats to its followers to ensure that leader stays elected as the leader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)