ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9722) MVCC: Test CacheMvccTransactionTest.testMvccCoordinatorChangeSimple fails.
Date Wed, 03 Oct 2018 11:33:00 GMT

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

Vladimir Ozerov commented on IGNITE-9722:
-----------------------------------------

Test run: https://ci.ignite.apache.org/viewQueued.html?itemId=1997412&tab=queuedBuildOverviewTab

> MVCC: Test CacheMvccTransactionTest.testMvccCoordinatorChangeSimple fails.
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-9722
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9722
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, mvcc
>            Reporter: Andrew Mashenkov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 2.7
>
>
> The test make transactional putAll() and then check data with Scan query and getAll().
> ScanQuery can miss some results on unstable topology which is expected as it doesn't
lock topology.
> But getAll() can unexpectedly return stale results.
> To reproduce the issue, one can change read mode SCAN->GET (passed to checkAndGetAll()
call) in checkPutGet() method. 
>  
> It looks like rebalance can overwrite local backup entries or remap is broken and we
read local partition in moving state. Disabling fastLocGet in GridPartitionedGetFuture.map()
resolves the issue.
>  



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

Mime
View raw message