[CONTROLLER-1164] Clustering : RaftActor should always use a scheduled heartbeat Created: 18/Feb/15  Updated: 24/Feb/15  Resolved: 24/Feb/15

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Post-Helium
Fix Version/s: None

Type: Bug
Reporter: Moiz Raja Assignee: Moiz Raja
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 2733

 Description   

The behavior of the RaftActor#Leader is that when a message comes in it reschedules the heartbeat regardless of what the message is. This can lead to a slow follower possibly being starved in a situation where a fast follower keeps sending an AppendEntriesReply. In this situation the fast follower will keep getting more AppendEntries whereas the slow follower will not because the heartbeat mechanism which is supposed to send the AppendEntries to the second follower keeps getting rescheduled.

One possible fix for this is to simply keep a scheduled heartbeat regardless of other messages that may come in.



 Comments   
Comment by Moiz Raja [ 24/Feb/15 ]

https://git.opendaylight.org/gerrit/#/c/15476/

Generated at Wed Feb 07 19:54:51 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.