You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/02/05 13:31:00 UTC
[jira] [Commented] (IGNITE-10604) MVCC: mvcc history can be missed during remove operation.

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

Ignite TC Bot commented on IGNITE-10604:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3004164&amp;buildTypeId=IgniteTests24Java8_RunAll]

> MVCC: mvcc history can be missed during remove operation.
> ---------------------------------------------------------
>
>                 Key: IGNITE-10604
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10604
>             Project: Ignite
>          Issue Type: Bug
>          Components: data structures, mvcc
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>            Priority: Major
>              Labels: failover, mvcc_stabilization_stage_1
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover fails on closing IgniteAtomicLong datastructure.
> CacheLateAffinityAssignmentTest.testNoForceKeysRequests() failed with same error.
> The root cause is DhtEnlist request for REMOVE operation with no history fails on MOVING partition.
>  
> {noformat}
> [2018-12-07 20:05:14,674][ERROR][sys-stripe-6-#10748%dht.IgniteAtomicLongChangingTopologySelfTest3%][IgniteTestResources] Critical system error detected. Will be handled accordingly to configured handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=SingletonSet [SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, err=java.lang.AssertionError]]
> java.lang.AssertionError
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.addToBatch(GridDhtTxAbstractEnlistFuture.java:701)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.processEntry(GridDhtTxAbstractEnlistFuture.java:651)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:534)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxEnlistRequest(GridDhtTransactionalCacheAdapter.java:2065)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$900(GridDhtTransactionalCacheAdapter.java:112)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$14.apply(GridDhtTransactionalCacheAdapter.java:229)
> at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$14.apply(GridDhtTransactionalCacheAdapter.java:227)
> {noformat}



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