You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 06:33:05 UTC
[jira] [Updated] (IGNITE-9428) MVCC TX:
MvccQueryTrackerImpl.onDone() semantic is broken.
[ https://issues.apache.org/jira/browse/IGNITE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-9428:
------------------------------------
Labels: transactions (was: mvcc_stabilization_stage_1 transactions)
> MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
> ----------------------------------------------------------
>
> Key: IGNITE-9428
> URL: https://issues.apache.org/jira/browse/IGNITE-9428
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
> Reporter: Roman Kondakov
> Priority: Major
> Labels: transactions
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Due to IGNITE-9256 patch, multiple {{H2ResultSetIterator#onClose}} invocation becomes possible. This can be considered as a {{Closable}} contract violation and should be fixed.
> Also this case revealed a bug in {{MvccQueryTrackerImpl}} when multiple {{onDone()}} call leads to multiple query finished acks sent back to the {{MvccCoordinator}} which leads to the problems with the query tracking and assertion errors.
> Reproducer: {{CacheMvccSqlTxQueriesAbstractTest#testAccountsTxDmlSumSql_WithRemoves_SingleNode}}
>
> Upd: test was fixed in IGNITE-9373. But MvccQueryTrackerImpl.onDone() issue is still actual.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)