You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/09/02 23:57:21 UTC
[jira] [Updated] (IGNITE-3479) Global transaction ordering
[ https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-3479:
--------------------------------
Labels: important (was: )
> Global transaction ordering
> ---------------------------
>
> Key: IGNITE-3479
> URL: https://issues.apache.org/jira/browse/IGNITE-3479
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Alexey Goncharuk
> Labels: important
> Fix For: 2.0
>
>
> Current transaction ID will not work for SQL MVCC ordering because two transaction IDs are not in total order across the cluster.
> One of the approaches is to have a dedicated coordinator which will assign a continuously growing transaction ID for each committed transaction. This ID must be acquired by each transaction at the last step of PREPARE stage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)