You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2019/03/20 16:21:00 UTC
[jira] [Comment Edited] (IGNITE-10550) MVCC: rework IgniteWalFlush*
tests for mvcc.
[ https://issues.apache.org/jira/browse/IGNITE-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797309#comment-16797309 ]
Andrew Mashenkov edited comment on IGNITE-10550 at 3/20/19 4:20 PM:
--------------------------------------------------------------------
The reason is DhtTxPrepareFuture.onComplete() method fails with exception right before mark the future as completed.
Catch exception thrown from tx.state() and tx invalidation resolve the issue.
Seems, it is partial fix and we have to add IgniteCheckedException in tx.state() method signature and correctly catch exception in all the places.
was (Author: amashenkov):
The reason is DhtTxPrepareFuture.onComplete() method fails with exception right before mark the future as completed.
Catch exception thrown from tx.state() and tx invalidation resolve the issue.
> MVCC: rework IgniteWalFlush* tests for mvcc.
> --------------------------------------------
>
> Key: IGNITE-10550
> URL: https://issues.apache.org/jira/browse/IGNITE-10550
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Major
> Labels: WAL
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Next tests failed in mvcc mode, most likely due to different MVCC tx semantic:
> * IgniteWalFlushBackgroundSelfTest
> * IgniteWalFlushBackgroundWithMmapBufferSelfTest
> * IgniteWalFlushFsyncSelfTest
> * IgniteWalFlushFsyncWithDedicatedWorkerSelfTest
> * IgniteWalFlushFsyncWithMmapBufferSelfTest
> * IgniteWalFlushLogOnlySelfTest
> * IgniteWalFlushLogOnlyWithMmapBufferSelfTest
> We have to create similar tests for mvcc mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)