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

Vladislav Pyatkov updated IGNITE-20894:
---------------------------------------
    Description: 
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:
Reproduced by [1]

In short, two transaction are put into deadlock, using no prevention policy.

First tx is committed, but can't acquire locks.

Expected behavior - tx is rolled back on commit, releasing associated locks, 
tx2 succefully commits.

Actual behavior - commit hangs.

[1] org.apache.ignite.distributed.ItLockTableTest#testDeadlockRecovery


> 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
>
>
> 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)

Reply via email to