ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Seliverstov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3479) Coordinator(s) for global transaction ordering
Date Fri, 06 Apr 2018 12:11:00 GMT

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

Igor Seliverstov updated IGNITE-3479:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> Coordinator(s) for global transaction ordering
> ----------------------------------------------
>
>                 Key: IGNITE-3479
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3479
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Alexey Goncharuk
>            Assignee: Semen Boikov
>            Priority: Major
>             Fix For: 2.6
>
>
> 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
(v7.6.3#76005)

Mime
View raw message