[jira] [Resolved] (IGNITE-3479) Coordinator(s) for global transaction ordering

["Semen Boikov (JIRA)" <ji...@apache.org>]

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

Semen Boikov resolved IGNITE-3479.
----------------------------------
    Resolution: Fixed

As first step implemented automatic coordinator assignment (oldest server node), implemented protocol for coordinator change in case of old coordinator failure + coordinator change support for 'getAll' operation, added basic tests to prove main mechanisms work.

> Coordinator(s) for 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
>            Assignee: Semen Boikov
>
> 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.4.14#64029)