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:49:18 UTC

[jira] [Updated] (KUDU-489) Implement a mechanism to make consensus terms serializable and persistent

     [ https://issues.apache.org/jira/browse/KUDU-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy updated KUDU-489:
----------------------------
    Parent: KUDU-433

> Implement a mechanism to make consensus terms serializable and persistent
> -------------------------------------------------------------------------
>
>                 Key: KUDU-489
>                 URL: https://issues.apache.org/jira/browse/KUDU-489
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: consensus
>    Affects Versions: M4
>            Reporter: David Alves
>            Assignee: Mike Percy
>            Priority: Critical
>   Original Estimate: 16h
>  Remaining Estimate: 16h
>
> Consensus terms must be serializable. That is
> a majority of replicas must agree, across reboots, who was voted/elected leader, if anyone, for all terms.
> To achieve this we need some kind of consensus metadata persistence and we need a serialization mechanism that implements this.
> The raft paper/logcabin impl/paxos in general should be a reference in this regard



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)