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/15 13:56:00 UTC

[jira] [Commented] (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=16793643#comment-16793643 ] 

Andrew Mashenkov commented on IGNITE-10550:
-------------------------------------------

Looks like remote tx type (mvcc\non-mvcc) is determined in wrong way.
 IgniteTxRemoteStateAdapter.mvccEnabled() always returns false as writeMap is always false for mvcc transactions.

> 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
>            Priority: Major
>              Labels: WAL
>             Fix For: 2.8
>
>
> 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)