[
https://issues.apache.org/jira/browse/IGNITE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797185#comment-17797185
]
Vladislav Pyatkov commented on IGNITE-20894:
--------------------------------------------
There are tests that demonstrate exactly one transaction commit preset for SQL:
_ItSqlApiBaseTest#checkTransactionsWithDml_
_ItSqlApiBaseTest#testLockIsNotReleasedAfterTxRollback_
If a transaction coordinator catches a lock exception, the transaction will be
automatically rolled back.
> Fix deadlock recovery on commit
> -------------------------------
>
> 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
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
