[jira] [Updated] (KUDU-131) Make replica/replayed transactions take the same timestamp as the original ones

["Mike Percy (JIRA)" <ji...@apache.org>]

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

Mike Percy updated KUDU-131:
----------------------------
    Parent: KUDU-430

> Make replica/replayed transactions take the same timestamp as the original ones
> -------------------------------------------------------------------------------
>
>                 Key: KUDU-131
>                 URL: https://issues.apache.org/jira/browse/KUDU-131
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: tablet
>    Affects Versions: M3
>            Reporter: David Alves
>            Assignee: David Alves
>            Priority: Critical
>
> Right now there is no guarantee that replayed transactions get the same id as the original ones. This is a problem because it will make replicas disagree on what should come out under a snapshot.
> Moreover Tablet's MvccManager must be forced never to produce txids below the last replayed transaction and replayed transactions should take the timestamps of the original ones.
> Finally there should be a system in place to advance replica timestmap so that are as close to the leader as possible.



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