[
https://issues.apache.org/jira/browse/IGNITE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-20894:
---------------------------------------
Description:
h3. Motivation
The first purpose of the transaction flow tests is to preserve consistency in
storage. The reason for this might be partial commits due to executing commits
and rollbacks on one transaction. The second is avoiding redundant or permanent
locks that can originate from an asynchronous operation during a commit.
h3. Definition of done
Here is a list of tests that should be present:
# Ensure the correctness of the exception and all the transaction's locks are
freed when adding operations to a committed transaction.
# Ensure the correctness of the exception and all the transaction's locks are
freed when adding operations to a rolled-back transaction.
# Test consistency after commit when the transaction is acting asynchronously.
# Test consistency after rollback when the transaction is acting asynchronously.
# Ensure consistency when a transaction is committed or rolled back from
several threads at the same time.
was:
Here is a list of tests that should be present:
# Ensure the correctness of the exception and all the transaction's locks are
freed when adding operations to a committed transaction.
# Ensure the correctness of the exception and all the transaction's locks are
freed when adding operations to a rolled-back transaction.
# Test consistency after commit when the transaction is acting asynchronously.
# Test consistency after rollback when the transaction is acting asynchronously.
# Ensure consistency when a transaction is committed or rolled back from
several threads at the same time.
> Add tests for ensuring transactional guarantees
> -----------------------------------------------
>
> Key: IGNITE-20894
> URL: https://issues.apache.org/jira/browse/IGNITE-20894
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
>
> h3. Motivation
> The first purpose of the transaction flow tests is to preserve consistency in
> storage. The reason for this might be partial commits due to executing
> commits and rollbacks on one transaction. The second is avoiding redundant or
> permanent locks that can originate from an asynchronous operation during a
> commit.
> h3. Definition of done
> Here is a list of tests that should be present:
> # Ensure the correctness of the exception and all the transaction's locks are
> freed when adding operations to a committed transaction.
> # Ensure the correctness of the exception and all the transaction's locks are
> freed when adding operations to a rolled-back transaction.
> # Test consistency after commit when the transaction is acting asynchronously.
> # Test consistency after rollback when the transaction is acting
> asynchronously.
> # Ensure consistency when a transaction is committed or rolled back from
> several threads at the same time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
