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

Vladislav Pyatkov updated IGNITE-23988:
---------------------------------------
    Description: 
h3. Motivation

We started to check RO transaction state to prevent process operation by fixed 
transaction (IGNITE-23980). But we still might process operations through the 
rece of checking and concurrent commit/rollback.
h3. Definition of done
 * Race between commit/rollbacl and an operation is not possible
 * An operation can be either executed (return result) or declined (with the 
exception that the RO transaction was closed).
 * The inflights approach have to work for KV and SQL

 

  was:
h3. Motivation

We started to check RO transaction state to prevent process operation by fixed 
transaction (IGNITE-23980). But we still might process operations through the 
rece of checking and concurrent commit/rollback.
h3. Definition of done
 * Race between commit/rollbacl and an operation is not possible
 * An operation can be either executed (return result) or declined (with the 
exception that the RO transaction was closed).


> Implement inflight operations for RO transactions
> -------------------------------------------------
>
>                 Key: IGNITE-23988
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23988
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>
> h3. Motivation
> We started to check RO transaction state to prevent process operation by 
> fixed transaction (IGNITE-23980). But we still might process operations 
> through the rece of checking and concurrent commit/rollback.
> h3. Definition of done
>  * Race between commit/rollbacl and an operation is not possible
>  * An operation can be either executed (return result) or declined (with the 
> exception that the RO transaction was closed).
>  * The inflights approach have to work for KV and SQL
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to