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-487) Implement transaction/operation abort

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

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

> Implement transaction/operation abort
> -------------------------------------
>
>                 Key: KUDU-487
>                 URL: https://issues.apache.org/jira/browse/KUDU-487
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: consensus, tserver
>    Affects Versions: M4
>            Reporter: David Alves
>            Assignee: David Alves
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> We might need to abort operations/transactions in certain cases. For instance when a leader gets disconnected from a majority of the quorum, and a new leader is elected, its non-majority replicated operations must be aborted. Similarly a replica that received a minority replicated operation from a leader might see that operation nullified by a subsequent leader.
> Aborting operations means:
> - cancelling ongoing transaction on all peers
> - have operation status trackers return a status on Wait()
> I started on this a while ago but this fell through the cracks as it was low pri then.



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