ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3479) Coordinator(s) for global transaction ordering
Date Fri, 04 Aug 2017 10:42:02 GMT

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

Semen Boikov updated IGNITE-3479:
    Summary: Coordinator(s) for global transaction ordering  (was: Global transaction ordering)

> 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
>             Fix For: 2.2
> 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

View raw message