{"push_id":572328613,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"1fbedd9f6b3ec25266c69ed0339a528fee533ca6","before":"05f8f86227bfd107e536684f9c593f5aeacb2811","commits":[{"sha":"ae3b5e9fca4f01878dae38b42e5d52598c4bddda","author":{"email":"8fc992100aff336363d341c5498f75ab4da389ae@brocade.com","name":"tpantelis"},"message":"Initial heartbeats not sent by Leader\n\nWhen a Leader instance is created, it immediately sends out heartbeats\nto the followers. However recent changes broke this behavior as\nsendAppendEntries now checks if the follower's timeSinceLastActivity >=\nheartbeat interval. However, in this case, timeSinceLastActivity is 0 so\nthe initial heartbeats aren't sent out. Also, on replication, it seems\nthat sendAppendEntries should always send AppendEntries. So we want to\ndisable this checking in these 2 cases. We only want check\ntimeSinceLastActivity if it's initiated by a scheduled heartbeat.\n\nTo resolve this, I changed the Leader constructor to directly call\nsendAppendEntries instead of scheduling SendHeartbeat with delay 0. I\nnow pass in the interval to sendAppendEntries. The scheduled heartbeat\npasses in the actual heartbeat interval and the oher 2 calls pass in 0.\n\nSeveral unit tests in LeaderTest had to be changed due to the new\nbehavior.\n\nChange-Id: I138db649b49ca18070a3247312521daf0dabc88e\nSigned-off-by: tpantelis <tpanteli@brocade.com>","distinct":true,"url":"https://api.github.com/repos/opendaylight/controller/commits/ae3b5e9fca4f01878dae38b42e5d52598c4bddda"},{"sha":"1fbedd9f6b3ec25266c69ed0339a528fee533ca6","author":{"email":"a0248e9982316d46e09a09fbbfb21cc58d7cc4d2@cisco.com","name":"Moiz Raja"},"message":"Merge \"Initial heartbeats not sent by Leader\"","distinct":true,"url":"https://api.github.com/repos/opendaylight/controller/commits/1fbedd9f6b3ec25266c69ed0339a528fee533ca6"}]}