You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/01/22 12:44:01 UTC

[jira] [Commented] (IGNITE-10520) MVCC: Next to mvcc-tx non-mvcc-Tx failed with unexpected exception.

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

Ivan Pavlukhin commented on IGNITE-10520:
-----------------------------------------

[~amashenkov] could you double check that ticket is relevant? Test contains code:
{code}
checkPutGet(ignite.cache(TX_CACHE), ignite.transactions(), OPTIMISTIC, REPEATABLE_READ);
{code}
and it is not surprise that it fails in {{FORCE_MVCC}} mode.

> MVCC: Next to mvcc-tx non-mvcc-Tx failed with unexpected exception.
> -------------------------------------------------------------------
>
>                 Key: IGNITE-10520
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10520
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Andrew Mashenkov
>            Assignee: Ivan Pavlukhin
>            Priority: Critical
>              Labels: mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>
>
> IgniteCachePrimarySyncTest.testPutGet) failed.
> It run tx operations one by one
>  # tx on Transactional cache
>  # tx on Transactional_snapshot cache.
>  # tx on Transactional cache
> Last tx failed with "TransactionException: Only pessimistic repeatable read transactions are supported when MVCC is enabled." which is unexpected.
> Looks like we forget to reset tx context somewhere.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)