You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2016/07/14 01:30:20 UTC

[jira] [Created] (IGNITE-3479) Global transaction ordering

Alexey Goncharuk created IGNITE-3479:
----------------------------------------

             Summary: 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
             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)