[
https://issues.apache.org/jira/browse/IGNITE-19731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735779#comment-17735779
]
Vladislav Pyatkov commented on IGNITE-19731:
--------------------------------------------
Really, the root cause of the issue was in only one test, but failed too many.
The reason by which several test may fail after a bug in one, is pending
transactions. In most methods in KV API we rollback transaction automatically
when a transaction exception happens (look at InternalTableImpl#postEnlist).
But specific scans methods which are used in SQL do nothing when some exception
happened or closing cursor (look at parameter value onClose for
PartitionScanPublisher). Due to this, behavior the transaction which is failed
(by lock conflict reason, for example) can fail the transaction (hence, the
corresponding test) in next tests.
> ItTableScanTest different test failed.
> --------------------------------------
>
> Key: IGNITE-19731
> URL: https://issues.apache.org/jira/browse/IGNITE-19731
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Attachments: image-2023-06-14-09-56-02-062.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ItTableScanTest different tests are failed, reproduced locally (just call run
> until failure and on 5+ iteration it will fail) main
> (79a841d95247c338b80ab91a93ec18ee7) TC also decide them flaky
> !image-2023-06-14-09-56-02-062.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
