[jira] [Commented] (RATIS-153) Add continuous heartbeats between Ratis servers to avoid unnecessary leader elections

["Mukul Kumar Singh (JIRA)" <ji...@apache.org>]

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

Mukul Kumar Singh commented on RATIS-153:
-----------------------------------------

Had an offline chat with [~ljain], There is already a notion of empty append entries which signifies heart beats. Need to debug further the reason for Leader elections in Ozone unit tests.

> Add continuous heartbeats between Ratis servers to avoid unnecessary leader elections
> -------------------------------------------------------------------------------------
>
>                 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
>
> 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
(v6.4.14#64029)