You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/02/26 12:55:18 UTC
[jira] [Updated] (KUDU-576) Don't trigger elections when waiting
for our own Log
[ https://issues.apache.org/jira/browse/KUDU-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Percy updated KUDU-576:
----------------------------
Parent: KUDU-560
> Don't trigger elections when waiting for our own Log
> ----------------------------------------------------
>
> Key: KUDU-576
> URL: https://issues.apache.org/jira/browse/KUDU-576
> Project: Kudu
> Issue Type: Sub-task
> Components: consensus
> Affects Versions: M4.5
> Reporter: David Alves
> Assignee: David Alves
>
> When log appends take a long time followers can go a while without resetting the timer. If the log append takes long enough then it's likely that when it completes it will have caused all the timers to fire triggering leader elections.Local log appends taking a long time should not cause leader elections to fire.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)