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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/08/16 15:23:00 UTC

[jira] [Updated] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails.

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

Vladimir Ozerov updated IGNITE-8841:
------------------------------------
    Component/s: mvcc

> MVCC TX: Read transactions remap when coordinator fails.
> --------------------------------------------------------
>
>                 Key: IGNITE-8841
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8841
>             Project: Ignite
>          Issue Type: Improvement
>          Components: mvcc, sql
>            Reporter: Roman Kondakov
>            Priority: Major
>              Labels: failover
>
> At the moment all read transactions are forcibly rolled back during coordinator change. It would be nice to remap it somehow until they locked a topology. For example, it is possible to obtain a new "write" mvcc version from the new coordinator and use this version for all further writes while using "old" version for reads. In this case we need to change visibility rules a little: "old" version should see "own" updates made by "new" "write" version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)