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

Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2018/07/24 17:00:00 UTC

[jira] [Updated] (IGNITE-8906) SQL TX: Immediate rollback for Near transactions during topology changing.

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

Dmitriy Pavlov updated IGNITE-8906:
-----------------------------------
    Description: At the moment all near transaction that was active during PME, but hadn't locked topology (i.e. read transactions), are marked as rollback only in GridDhtPartitionsExchangeFuture#onDone. But it is better to stop transaction execution immediately to prevent useless updates.   (was: At the moment all near transaction that was active during PME, but hadn't locked topology (i.e. read transactions), are marked as rollback only in GridDhtPartitionsExchangeFuture#onDone. But it is better to stop transaction execution immediately to prevent useless updates.)

> SQL TX: Immediate rollback for Near transactions during topology changing.
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-8906
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8906
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Roman Kondakov
>            Assignee: Roman Kondakov
>            Priority: Major
>              Labels: mvcc
>
> At the moment all near transaction that was active during PME, but hadn't locked topology (i.e. read transactions), are marked as rollback only in GridDhtPartitionsExchangeFuture#onDone. But it is better to stop transaction execution immediately to prevent useless updates. 



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