[
https://issues.apache.org/jira/browse/IGNITE-17806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618916#comment-17618916
]
Sergey Uttsel edited comment on IGNITE-17806 at 10/18/22 3:06 PM:
------------------------------------------------------------------
The test checks that there are no tx with PENDING state in
TxManagerImpl#states. Now tx coordinator put PENDING state on
TxManagerImpl#begin. But not removed if tx doesn't enlist partitions.
I think no need to save state on tx begin and we can remove PENDING status.
was (Author: sergey uttsel):
The test checks that there are no tx with PENDING state in
TxManagerImpl#states. Now tx coordinator put PENDING state on
TxManagerImpl#begin. But not removed if tx doesn't enlist partitions.
I think no need to save state on tx begin.
> Rollback SQL automatically created transaction when an error has happened
> -------------------------------------------------------------------------
>
> Key: IGNITE-17806
> URL: https://issues.apache.org/jira/browse/IGNITE-17806
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> In some cases, when the used does not pass a transaction explicit to SQL, the
> engine (SQLProcessor) creates a new one transaction automatically. When
> during the execution an exception is thrown, the automatically created
> transaction is not rolled back and freezes in pending state.
> Look at the test to find out the issue: _ItSqlSynchronousApiTest#errors_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
