[jira] [Commented] (OMID-146) Persist transaction commit before updating low watermark

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OMID-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820269#comment-16820269 ] 

Lars Hofhansl commented on OMID-146:
------------------------------------

1.0 .1 needs to be delayed until this is fixed?

> Persist transaction commit before updating low watermark
> --------------------------------------------------------
>
>                 Key: OMID-146
>                 URL: https://issues.apache.org/jira/browse/OMID-146
>             Project: Apache Omid
>          Issue Type: Bug
>            Reporter: Ohad Shacham
>            Assignee: Yonatan Gottesman
>            Priority: Minor
>             Fix For: 1.0.1
>
>
> When a transaction t updates the conflict table at the TSO, it mights remove entries of transactions that committed after t started, or even entries of t. Therefore, in order to make sure that the garbage collector does not removes entries of t from the data tables, thinking accidentally that t was not committed yet. We should first persist t's commit in the commit table and only then update the low watermark. This also applies to the low latency which persists the commit by the clients.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)