ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9428) MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
Date Fri, 21 Sep 2018 17:43:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623934#comment-16623934

Andrew Mashenkov commented on IGNITE-9428:

[~rkondakov], [~gvvinblade],

Would you please review changes?

> 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
>            Assignee: Andrew Mashenkov
>            Priority: Major
>             Fix For: 2.7
> 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

This message was sent by Atlassian JIRA

View raw message