[jira] [Created] (IGNITE-10766) MVCC: CacheMvccTxRecoveryTest.testCountersNeighborcastServerFailed fails sporadically
Roman Kondakov created IGNITE-10766:
---
Summary: MVCC:
CacheMvccTxRecoveryTest.testCountersNeighborcastServerFailed fails sporadically
Key: IGNITE-10766
URL: https://issues.apache.org/jira/browse/IGNITE-10766
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
{{CacheMvccTxRecoveryTest.testCountersNeighborcastServerFailed}} sporadically
jangs on exchange. It should be investigated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10765) MVCC: MvccReplicatedTxPessimisticOriginatingNodeFailureRecoveryTest.testManyKeysRollback fails sometimes
Roman Kondakov created IGNITE-10765:
---
Summary: MVCC:
MvccReplicatedTxPessimisticOriginatingNodeFailureRecoveryTest.testManyKeysRollback
fails sometimes
Key: IGNITE-10765
URL: https://issues.apache.org/jira/browse/IGNITE-10765
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
{{MvccReplicatedTxPessimisticOriginatingNodeFailureRecoveryTest.testManyKeysRollback}}
fails sometimes. See trace bellow.
{noformat}
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteTxPessimisticOriginatingNodeFailureAbstractSelfTest.testTxOriginatingNodeFails(IgniteTxPessimisticOriginatingNodeFailureAbstractSelfTest.java:260)
at
org.apache.ignite.internal.processors.cache.distributed.IgniteTxPessimisticOriginatingNodeFailureAbstractSelfTest.testManyKeysRollback(IgniteTxPessimisticOriginatingNodeFailureAbstractSelfTest.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2121)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout
Roman Kondakov created IGNITE-10764:
---
Summary: MVCC: Transactions failed to acquire lock within timeout
Key: IGNITE-10764
URL: https://issues.apache.org/jira/browse/IGNITE-10764
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
Some tests failed sporadically due to a transaction timeout though they update
unique keys and deadlocks are not expected. It should be investigated.
Reproducers:
{{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
{{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10752) MVCC: Tests invariants are violated sometimes
[
https://issues.apache.org/jira/browse/IGNITE-10752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10752:
Description:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
**
{{testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups1_CoordinatorFails}}
** {{testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
** {{testGetReadInProgressCoordinatorFails}}
** {{testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
* {{CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple}}
* {{DataStreamProcessorMvccPersistenceSelfTest.testTryFlush}}
* {{IgniteCacheGroupsTest.testCreateDestroyCachesMvccTxReplicated}}
*
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups0_Sql_Persistence}}
* {{CacheMvccPartitionedSqlCoordinatorFailoverTest}}
** {{testUpdate_N_Objects_ClientServer_Backups2_Sql}}
**
{{testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml}}
** {{testPutAllGetAll_Server_Backups1_SinglePartition_RestartRandomSrv_SqlDml}}
** {{testAccountsTxSql_Server_Backups0_CoordinatorFails}}
** {{testAccountsTxSql_Server_Backups1_CoordinatorFails_Persistence}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
was:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
**
{{testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups1_CoordinatorFails}}
** {{testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
** {{testGetReadInProgressCoordinatorFails}}
** {{testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
* {{CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple}}
* {{DataStreamProcessorMvccPersistenceSelfTest.testTryFlush}}
* {{IgniteCacheGroupsTest.testCreateDestroyCachesMvccTxReplicated}}
*
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups0_Sql_Persistence}}
* {{CacheMvccPartitionedSqlCoordinatorFailoverTest}}
** {{testUpdate_N_Objects_ClientServer_Backups2_Sql}}
**
{{testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml}}
** {{testPutAllGetAll_Server_Backups1_SinglePartition_RestartRandomSrv_SqlDml}}
** {{testAccountsTxSql_Server_Backups0_CoordinatorFails}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
> MVCC: Tests invariants are violated sometimes
>
[jira] [Created] (IGNITE-10763) MVCC: Transaction already completed error in some tests
Roman Kondakov created IGNITE-10763:
---
Summary: MVCC: Transaction already completed error in some tests
Key: IGNITE-10763
URL: https://issues.apache.org/jira/browse/IGNITE-10763
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
"Transaction is already completed" error occurs time to time in some tests.
Reproducer:
{{CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction}}
{noformat}
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:832)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:813)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:796)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1131)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:1990)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1636)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1526)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2167)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2162)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2670)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$1(GridQueryProcessor.java:2176)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2196)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2157)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2118)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2091)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccReplicatedSqlTxQueriesTest.runSql(CacheMvccReplicatedSqlTxQueriesTest.java:234)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccReplicatedSqlTxQueriesTest.testReplicatedAndPartitionedUpdateSingleTransaction(CacheMvccReplicatedSqlTxQueriesTest.java:202)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2121)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10752) MVCC: Tests invariants are violated sometimes
[
https://issues.apache.org/jira/browse/IGNITE-10752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10752:
Description:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
**
{{testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups1_CoordinatorFails}}
** {{testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
** {{testGetReadInProgressCoordinatorFails}}
** {{testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
* {{CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple}}
* {{DataStreamProcessorMvccPersistenceSelfTest.testTryFlush}}
* {{IgniteCacheGroupsTest.testCreateDestroyCachesMvccTxReplicated}}
*
{{CacheMvccReplicatedSqlCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups0_Sql_Persistence}}
* {{CacheMvccPartitionedSqlCoordinatorFailoverTest}}
** {{testUpdate_N_Objects_ClientServer_Backups2_Sql}}
**
{{testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml}}
** {{testPutAllGetAll_Server_Backups1_SinglePartition_RestartRandomSrv_SqlDml}}
** {{testAccountsTxSql_Server_Backups0_CoordinatorFails}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
was:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
**
{{testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups1_CoordinatorFails}}
** {{testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
** {{testGetReadInProgressCoordinatorFails}}
** {{testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
* {{CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple}}
* {{DataStreamProcessorMvccPersistenceSelfTest.testTryFlush}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
> MVCC: Tests invariants are violated sometimes
> -
>
> Key: IGNITE-10752
> URL: https://issues.apache.org/jira/browse/IGNITE-10752
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> Sometimes tests are failed by violated invariants errors. For example, when
> total sum on accounts is not as expected.
> Muted tests:
> * {{CacheMvccPartitionedCoordinatorFailoverTest}}
> **
>
[jira] [Created] (IGNITE-10756) MVCC: Query trackers are not released sometimes
Roman Kondakov created IGNITE-10756:
---
Summary: MVCC: Query trackers are not released sometimes
Key: IGNITE-10756
URL: https://issues.apache.org/jira/browse/IGNITE-10756
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
Sometimes query trackers are not released when error occurs during iterating
over {{QueryCursor}}. It may be already fixed in IGNITE-10448. Need to check.
Affected tests:
* {{CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedPartitioned}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10755) MVCC: Flaky continuous query tests
[
https://issues.apache.org/jira/browse/IGNITE-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10755:
Description:
Some continuous query tests are flaky when MVCC is enabled:
* {{CacheContinuousQueryConcurrentPartitionUpdateTest}}
** {{testConcurrentUpdatesAndQueryStartMvccTxCacheGroup}}
** {{testConcurrentUpdatesAndQueryStartMvccTx}}
was:
Some continuous query tests are flaky when MVCC is enabled.
> MVCC: Flaky continuous query tests
> --
>
> Key: IGNITE-10755
> URL: https://issues.apache.org/jira/browse/IGNITE-10755
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: CQ, MakeTeamcityGreenAgain, mvcc_stabilization_stage_1
>
> Some continuous query tests are flaky when MVCC is enabled:
> * {{CacheContinuousQueryConcurrentPartitionUpdateTest}}
> ** {{testConcurrentUpdatesAndQueryStartMvccTxCacheGroup}}
> ** {{testConcurrentUpdatesAndQueryStartMvccTx}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10448) MVCC: NPE on data page eviction.
[
https://issues.apache.org/jira/browse/IGNITE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725853#comment-16725853
]
Roman Kondakov commented on IGNITE-10448:
-
[~gvvinblade], tests look good. Ready for review.
> MVCC: NPE on data page eviction.
>
>
> Key: IGNITE-10448
> URL: https://issues.apache.org/jira/browse/IGNITE-10448
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, pagememory
>
> NPE occurred during page eviction process.
> Reproducer: {{PageEvictionMultinodeMixedRegionsTest}}.
> StackTrace:
>
> {noformat}
> javax.cache.CacheException: class
> org.apache.ignite.transactions.TransactionRollbackException: Transaction has
> been rolled back: 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.createCacheAndTestEvcition(PageEvictionMultinodeAbstractTest.java:101)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.testPageEviction(PageEvictionMultinodeAbstractTest.java:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.transactions.TransactionRollbackException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:923)
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:921)
> ... 15 more
> Caused by: class
> org.apache.ignite.internal.transactions.IgniteTxRollbackCheckedException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4299)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2520)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2501)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2478)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> backup node: [localNodeId=0d817370-17fe-46f1-85ef-ea74b6f1,
> remoteNodeId=ebab34f3-abbc-47e9-90fa-a48a8260]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2340)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1059)
> at
>
[jira] [Created] (IGNITE-10755) MVCC: Flaky continuous query tests
Roman Kondakov created IGNITE-10755: --- Summary: MVCC: Flaky continuous query tests Key: IGNITE-10755 URL: https://issues.apache.org/jira/browse/IGNITE-10755 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Roman Kondakov Some continuous query tests are flaky when MVCC is enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10753) MVCC: Sometimes vacuum does not cleanup all outdated versions
[
https://issues.apache.org/jira/browse/IGNITE-10753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10753:
Description:
When mvcc test is finished, we check if there any outdated versions are left in
cache and not cleaned by vacuum. If so, an exception is thrown. There are some
tests with this problem:
* {{CacheMvccTransactionsTest.testCleanupWaitsForGet1}}
* {{CacheMvccTransactionsTest.testCleanupWaitsForGet3}}
was:
When mvcc test is finished, we check if there any outdated versions are left in
cache and not cleaned by vacuum. If so, an exception is thrown. There are some
tests with this problem:
* {{CacheMvccTransactionsTest.testCleanupWaitsForGet1}}
> MVCC: Sometimes vacuum does not cleanup all outdated versions
> -
>
> Key: IGNITE-10753
> URL: https://issues.apache.org/jira/browse/IGNITE-10753
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1,
> transactions
>
> When mvcc test is finished, we check if there any outdated versions are left
> in cache and not cleaned by vacuum. If so, an exception is thrown. There are
> some tests with this problem:
> * {{CacheMvccTransactionsTest.testCleanupWaitsForGet1}}
> * {{CacheMvccTransactionsTest.testCleanupWaitsForGet3}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10752) MVCC: Tests invariants are violated sometimes
[
https://issues.apache.org/jira/browse/IGNITE-10752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10752:
Description:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
**
{{testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups1_CoordinatorFails}}
** {{testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
** {{testGetReadInProgressCoordinatorFails}}
** {{testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
** {{testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
* {{CacheMvccTransactionsTest.testMvccCoordinatorChangeSimple}}
* {{DataStreamProcessorMvccPersistenceSelfTest.testTryFlush}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
was:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_SingleNode_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups1_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
> MVCC: Tests invariants are violated sometimes
> -
>
> Key: IGNITE-10752
> URL: https://issues.apache.org/jira/browse/IGNITE-10752
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> Sometimes tests are failed by violated invariants errors. For example, when
> total sum on accounts is not as expected.
> Muted tests:
> * {{CacheMvccPartitionedCoordinatorFailoverTest}}
> **
> {{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
> ** {{testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
> **
> {{testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
> ** {{testAccountsTxGet_SingleNode_CoordinatorFails}}
> ** {{testAccountsTxGet_Server_Backups1_CoordinatorFails}}
> ** {{testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
> **
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception in multithreaded tests
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Description:
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. This problem occurs both on stable and
unstable topologies.
These tests were muted on TC:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
** {{testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
** {{testAccountsTxScan_ClientServer_Backups2_CoordinatorFails}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
* {{CacheMvccTransactionsTest}}
** {{testUpdate_N_Objects_ClientServer_Backups2_Get}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception in multithreaded tests
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Description:
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. This problem occurs both on stable and
unstable topologies.
These tests were muted on TC:
* {{CacheMvccPartitionedCoordinatorFailoverTest}}
** {{testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
** {{testAccountsTxScan_ClientServer_Backups2_CoordinatorFails}}
* {{CacheMvccReplicatedCoordinatorFailoverTest}}
**
{{testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
** {{testAccountsTxScan_Server_Backups0_CoordinatorFails}}
* {{CacheMvccTransactionsTest}}
** {{testUpdate_N_Objects_ClientServer_Backups2_Get}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception in multithreaded tests
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Description:
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. This problem occurs both on stable and
unstable topologies.
These tests were muted on TC:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_ClientServer_Backups2_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups0_CoordinatorFails}}
* {{CacheMvccTransactionsTest.testUpdate_N_Objects_ClientServer_Backups2_Get}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception in multithreaded tests
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Description:
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. This problem occurs both on stable and
unstable topologies.
These tests were muted on TC:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_ClientServer_Backups2_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
* {{CacheMvccTransactionsTest.testUpdate_N_Objects_ClientServer_Backups2_Get }}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups0_CoordinatorFails}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
[jira] [Created] (IGNITE-10753) MVCC: Sometimes vacuum does not cleanup all outdated versions
Roman Kondakov created IGNITE-10753:
---
Summary: MVCC: Sometimes vacuum does not cleanup all outdated
versions
Key: IGNITE-10753
URL: https://issues.apache.org/jira/browse/IGNITE-10753
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
When mvcc test is finished, we check if there any outdated versions are left in
cache and not cleaned by vacuum. If so, an exception is thrown. There are some
tests with this problem:
* {{CacheMvccTransactionsTest.testCleanupWaitsForGet1}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10752) MVCC: Tests invariants are violated sometimes
[
https://issues.apache.org/jira/browse/IGNITE-10752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10752:
Description:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_SingleNode_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups1_CoordinatorFails}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
was:
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
> MVCC: Tests invariants are violated sometimes
> -
>
> Key: IGNITE-10752
> URL: https://issues.apache.org/jira/browse/IGNITE-10752
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> Sometimes tests are failed by violated invariants errors. For example, when
> total sum on accounts is not as expected.
> Muted tests:
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
> *
> {{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testGetReadInsideTxInProgressCoordinatorFails_ReadDelay}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_SingleNode_CoordinatorFails}}
> *
> {{CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups0_CoordinatorFails_Persistence}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_SingleNode__PutGet_CoordinatorFails}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_Server_Backups1_CoordinatorFails}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1_PutGet_CoordinatorFails_Persistence}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups1_CoordinatorFails_Persistence}}
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testAccountsTxGet_ClientServer_Backups2_CoordinatorFails_Persistence}}
> {noformat}
> junit.framework.AssertionFailedError: Unexpected error:
> junit.framework.AssertionFailedError: expected:<0> but was:<4>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
>
[jira] [Created] (IGNITE-10752) MVCC: Tests invariants are violated sometimes
Roman Kondakov created IGNITE-10752:
---
Summary: MVCC: Tests invariants are violated sometimes
Key: IGNITE-10752
URL: https://issues.apache.org/jira/browse/IGNITE-10752
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
Sometimes tests are failed by violated invariants errors. For example, when
total sum on accounts is not as expected.
Muted tests:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: expected:<0> but was:<4>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1362)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$10.call(CacheMvccAbstractTest.java:1350)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception in multithreaded tests
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Description:
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. This problem occurs both on stable and
unstable topologies.
These tests were muted on TC:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
* {{CacheMvccTransactionsTest.testUpdate_N_Objects_ClientServer_Backups2_Get }}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1966)
at
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception after coordinator fail
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Description:
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. These tests were muted on TC:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
* {{CacheMvccTransactionsTest.testUpdate_N_Objects_ClientServer_Backups2_Get }}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1966)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:544)
at
[jira] [Updated] (IGNITE-10750) MVCC: Unexpected tx state exception in multithreaded tests
[
https://issues.apache.org/jira/browse/IGNITE-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10750:
Summary: MVCC: Unexpected tx state exception in multithreaded tests (was:
MVCC: Unexpected tx state exception after coordinator fail)
> MVCC: Unexpected tx state exception in multithreaded tests
> --
>
> Key: IGNITE-10750
> URL: https://issues.apache.org/jira/browse/IGNITE-10750
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, failover,
> mvcc_stabilization_stage_1
>
> There is a number of tests in MVCC suite sporadically fail with the similar
> {{IgniteTxMvccVersionCheckedException}}. These tests were muted on TC:
> *
> {{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
> *
> {{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
> * {{CacheMvccTransactionsTest.testUpdate_N_Objects_ClientServer_Backups2_Get
> }}
>
>
> {noformat}
> junit.framework.AssertionFailedError: Unexpected error:
> junit.framework.AssertionFailedError: Unexpected tx exception.
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to update backup node:
> [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
> remoteNodeId=4198d600-48ee-4627-9802-0d157380]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
> at
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
> at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
> remoteNodeId=4198d600-48ee-4627-9802-0d157380]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> at
>
[jira] [Created] (IGNITE-10750) MVCC: Unexpected tx state exception after coordinator fail
Roman Kondakov created IGNITE-10750:
---
Summary: MVCC: Unexpected tx state exception after coordinator fail
Key: IGNITE-10750
URL: https://issues.apache.org/jira/browse/IGNITE-10750
Project: Ignite
Issue Type: Bug
Components: mvcc
Reporter: Roman Kondakov
There is a number of tests in MVCC suite sporadically fail with the similar
{{IgniteTxMvccVersionCheckedException}}. These tests were muted on TC:
*
{{CacheMvccPartitionedCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups1__PutGet_CoordinatorFails}}
*
{{CacheMvccReplicatedCoordinatorFailoverTest.testUpdate_N_Objects_Servers_Backups0__PutGet_CoordinatorFails_Persistence}}
{noformat}
junit.framework.AssertionFailedError: Unexpected error:
junit.framework.AssertionFailedError: Unexpected tx exception.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
Failed to update backup node:
[localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.putAll(IgniteCacheProxyImpl.java:1171)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.putAll(GatewayProtectedCacheProxy.java:868)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.writeAllByMode(CacheMvccAbstractTest.java:2021)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1143)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$7.apply(CacheMvccAbstractTest.java:1116)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1328)
at
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$9.call(CacheMvccAbstractTest.java:1323)
at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
backup node: [localNodeId=fd28ba5c-6216-4aaa-a496-ba24cee1,
remoteNodeId=4198d600-48ee-4627-9802-0d157380]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2342)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1127)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:391)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:108)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:307)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1070)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1966)
at
[jira] [Updated] (IGNITE-10063) MVCC SQL: Tx SQL commands are not supported in multistatements
[
https://issues.apache.org/jira/browse/IGNITE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10063:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC SQL: Tx SQL commands are not supported in multistatements
> --
>
> Key: IGNITE-10063
> URL: https://issues.apache.org/jira/browse/IGNITE-10063
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> Is is possible to execute multiple statements in single JDBC call like:
> {code:sql}UPDATE t1 SET b = '2'; COMMIT{code}
> Currently tx commands fail to execute if passed in such multistatement. Tx
> commands are e.g. {{BEGIN}}, {{COMMIT}}, {{ROLLBACK}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10054) sqlline hangs with concurrent operations
[
https://issues.apache.org/jira/browse/IGNITE-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10054:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> sqlline hangs with concurrent operations
>
>
> Key: IGNITE-10054
> URL: https://issues.apache.org/jira/browse/IGNITE-10054
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Critical
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
> Attachments: 15828.txt, 16696.txt, ignite-24507fea.0.log,
> ignite-c9ddebdb.0.log
>
>
> 1. Start 2 nodes cluster with PDS (wal_mode=FSYNC), activate
> 2. Start 1st {{bin/sqlline}} with following commands (in batch file):
> {noformat}
> create table t1 (a int, b int, primary key(a)) with
> "atomicity=TRANSACTIONAL_SNAPSHOT,backups=1";
> insert into t1 values (1,1);
> insert into t1 values (2,1);
> insert into t1 values (3,1);
> insert into t1 values (4,1);
> insert into t1 values (5,1);
> insert into t1 values (6,1);
> insert into t1 values (7,1);
> insert into t1 values (8,1);
> insert into t1 values (9,1);
> insert into t1 values (10,1);
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> ...repeat TX many times...
> {noformat}
> 3. Start 2nd {{bin/sqlline}} with following commands (in batch file):
> {noformat}
> begin;
> update t1 set b=b-1;
> commit;
> begin;
> update t1 set b=b-1;
> commit;
> begin;
> update t1 set b=b-1;
> commit;
> ...repeat TX many times...
> {noformat}
> 4. After some time both {{sqlline}} hang:
> {noformat}
> 611/113163 commit;
> Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
> transaction because it has been rolled back [t
> imeout=0,
> tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
> xidVersion=GridCacheVersion [topVer=1
> 52310006, order=154082519, nodeOrder=1], concurrency=PESSIMISTIC,
> isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
> invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
> label=null]]]
> (state=5,code=1)
> java.sql.SQLException: Failed to execute DDL statement [stmt=commit,
> err=Failed to finish transaction because it has bee
> n rolled back [timeout=0,
> tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
> xidVersion=GridCacheV
> ersion [topVer=152310006, order=154082519, nodeOrder=1],
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=M
> ARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11
> , label=null]]]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.runCommands(SqlLine.java:1706)
> at sqlline.Commands.run(Commands.java:1317)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:595)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 612/113163 begin;
> No rows affected (0 seconds)
> 613/113163 update t1 set b=b+1;
> {noformat}
> {noformat}
> Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
> transaction because it has been rolled back [t
> imeout=0,
> tx=GridNearTxLocal[xid=191ff90c661--0914-10f6--0001,
> xidVersion=GridCacheVersion [topVer=1
> 52310006, order=154082505, nodeOrder=1], concurrency=PESSIMISTIC,
> isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
> invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
> label=null]]]
> (state=5,code=1)
> java.sql.SQLException: Failed to execute DDL
[jira] [Updated] (IGNITE-9735) Determine partitions during parsing for MVCC DML statements
[
https://issues.apache.org/jira/browse/IGNITE-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9735:
---
Ignite Flags: (was: Docs Required)
> Determine partitions during parsing for MVCC DML statements
> ---
>
> Key: IGNITE-9735
> URL: https://issues.apache.org/jira/browse/IGNITE-9735
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> Now with for MVCC caches query like below is broadcasted instead of sending
> to single node only.
> {code:java}
> update table set _val = _val + 1 where _key = ?{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9735) Determine partitions during parsing for MVCC DML statements
[
https://issues.apache.org/jira/browse/IGNITE-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9735:
---
Labels: mvcc_stabilization_stage_1 transactions (was: )
> Determine partitions during parsing for MVCC DML statements
> ---
>
> Key: IGNITE-9735
> URL: https://issues.apache.org/jira/browse/IGNITE-9735
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Ivan Pavlukhin
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> Now with for MVCC caches query like below is broadcasted instead of sending
> to single node only.
> {code:java}
> update table set _val = _val + 1 where _key = ?{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10054) sqlline hangs with concurrent operations
[
https://issues.apache.org/jira/browse/IGNITE-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10054:
Ignite Flags: (was: Docs Required)
> sqlline hangs with concurrent operations
>
>
> Key: IGNITE-10054
> URL: https://issues.apache.org/jira/browse/IGNITE-10054
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.8
>
> Attachments: 15828.txt, 16696.txt, ignite-24507fea.0.log,
> ignite-c9ddebdb.0.log
>
>
> 1. Start 2 nodes cluster with PDS (wal_mode=FSYNC), activate
> 2. Start 1st {{bin/sqlline}} with following commands (in batch file):
> {noformat}
> create table t1 (a int, b int, primary key(a)) with
> "atomicity=TRANSACTIONAL_SNAPSHOT,backups=1";
> insert into t1 values (1,1);
> insert into t1 values (2,1);
> insert into t1 values (3,1);
> insert into t1 values (4,1);
> insert into t1 values (5,1);
> insert into t1 values (6,1);
> insert into t1 values (7,1);
> insert into t1 values (8,1);
> insert into t1 values (9,1);
> insert into t1 values (10,1);
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> begin;
> update t1 set b=b+1;
> commit;
> ...repeat TX many times...
> {noformat}
> 3. Start 2nd {{bin/sqlline}} with following commands (in batch file):
> {noformat}
> begin;
> update t1 set b=b-1;
> commit;
> begin;
> update t1 set b=b-1;
> commit;
> begin;
> update t1 set b=b-1;
> commit;
> ...repeat TX many times...
> {noformat}
> 4. After some time both {{sqlline}} hang:
> {noformat}
> 611/113163 commit;
> Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
> transaction because it has been rolled back [t
> imeout=0,
> tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
> xidVersion=GridCacheVersion [topVer=1
> 52310006, order=154082519, nodeOrder=1], concurrency=PESSIMISTIC,
> isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
> invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
> label=null]]]
> (state=5,code=1)
> java.sql.SQLException: Failed to execute DDL statement [stmt=commit,
> err=Failed to finish transaction because it has bee
> n rolled back [timeout=0,
> tx=GridNearTxLocal[xid=f91ff90c661--0914-10f6--0001,
> xidVersion=GridCacheV
> ersion [topVer=152310006, order=154082519, nodeOrder=1],
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=M
> ARKED_ROLLBACK, invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11
> , label=null]]]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.runCommands(SqlLine.java:1706)
> at sqlline.Commands.run(Commands.java:1317)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:595)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 612/113163 begin;
> No rows affected (0 seconds)
> 613/113163 update t1 set b=b+1;
> {noformat}
> {noformat}
> Error: Failed to execute DDL statement [stmt=commit, err=Failed to finish
> transaction because it has been rolled back [t
> imeout=0,
> tx=GridNearTxLocal[xid=191ff90c661--0914-10f6--0001,
> xidVersion=GridCacheVersion [topVer=1
> 52310006, order=154082505, nodeOrder=1], concurrency=PESSIMISTIC,
> isolation=REPEATABLE_READ, state=MARKED_ROLLBACK,
> invalidate=false, rollbackOnly=true,
> nodeId=c9ddebdb-c328-4283-97c5-a663887a, timeout=0, duration=11,
> label=null]]]
> (state=5,code=1)
> java.sql.SQLException: Failed to execute DDL statement [stmt=commit,
> err=Failed to finish transaction because it has bee
> n rolled
[jira] [Created] (IGNITE-10743) MVCC: Mute flaky mvcc tests
Roman Kondakov created IGNITE-10743: --- Summary: MVCC: Mute flaky mvcc tests Key: IGNITE-10743 URL: https://issues.apache.org/jira/browse/IGNITE-10743 Project: Ignite Issue Type: Task Components: mvcc Reporter: Roman Kondakov Assignee: Roman Kondakov We should mute all flaky MVCC tests on TC with appropriate tickets links. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7307) H2DynamicIndexingComplexServerTransactionalReplicatedTest.testOperations fails with assertion
[
https://issues.apache.org/jira/browse/IGNITE-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-7307:
---
Labels: transactions (was:
H2DynamicIndexingComplexServerTransactionalReplicatedTest. transactions)
> H2DynamicIndexingComplexServerTransactionalReplicatedTest.testOperations
> fails with assertion
> -
>
> Key: IGNITE-7307
> URL: https://issues.apache.org/jira/browse/IGNITE-7307
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> {code}
> [2017-12-26 11:40:53,187][ERROR][main][root] Test failed.
> java.lang.AssertionError: localNode = cde0ed21-5bfa-48ee-8e47-53d85880,
> dhtNodes = [TcpDiscoveryNode [id=49318149-4b22-40d1-b68f-8b6b2d52,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47501], discPort=47501, order=3,
> intOrder=3, lastExchangeTime=1514277649002, loc=false,
> ver=2.4.0#19700101-sha1:, isClient=false], TcpDiscoveryNode
> [id=cde0ed21-5bfa-48ee-8e47-53d85880, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1514277652494, loc=true, ver=2.4.0#19700101-sha1:,
> isClient=false], TcpDiscoveryNode [id=7530f231-3bd4-4cc0-b295-0e2f11b3,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=4,
> intOrder=4, lastExchangeTime=1514277649456, loc=false,
> ver=2.4.0#19700101-sha1:, isClient=false]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map(GridDhtTxPrepareFuture.java:1608)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1274)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1056)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsyncLocal(GridNearTxLocal.java:3619)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareColocatedTx(IgniteTxHandler.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.prepareLocal(GridNearPessimisticTxPrepareFuture.java:256)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.preparePessimistic(GridNearPessimisticTxPrepareFuture.java:406)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.prepare(GridNearPessimisticTxPrepareFuture.java:190)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3323)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:3390)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commit(GridNearTxLocal.java:3350)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:429)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:177)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:212)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1809)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1645)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:2034)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:2030)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2527)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:2039)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1995)
> at
>
[jira] [Updated] (IGNITE-9265) MVCC TX: Two rows with the same key in one MERGE statement produce an exception
[
https://issues.apache.org/jira/browse/IGNITE-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9265:
---
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC TX: Two rows with the same key in one MERGE statement produce an
> exception
> ---
>
> Key: IGNITE-9265
> URL: https://issues.apache.org/jira/browse/IGNITE-9265
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> In case the operation like {{MERGE INTO INTEGER (_key, _val) KEY(_key) VALUES
> (1,1),(1,2)}} is called an exception is occurred.
> Correct behavior: each next update on the same key overwrites pervious one
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7265) BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails
[
https://issues.apache.org/jira/browse/IGNITE-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-7265:
---
Labels: mvcc_stabilization_stage_1 pagememory (was: )
> BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails
>
>
> Key: IGNITE-7265
> URL: https://issues.apache.org/jira/browse/IGNITE-7265
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, pagememory
>
> {code}
> java.lang.AssertionError: Assertion error on row: 26
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2221)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.put(BPlusTree.java:2156)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.iterateConcurrentPutRemove(BPlusTreeSelfTest.java:2202)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.testIterateConcurrentPutRemove_1(BPlusTreeSelfTest.java:2169)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2008)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1923)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.AssertionError: 27
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.setLevelsCount(BPlusMetaIO.java:98)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.addRoot(BPlusMetaIO.java:155)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AddRoot.run(BPlusTree.java:661)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AddRoot.run(BPlusTree.java:650)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:277)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:241)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$10500(BPlusTree.java:82)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertWithSplit(BPlusTree.java:3073)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:2949)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$2500(BPlusTree.java:2831)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:420)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:401)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5153)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5138)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:342)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:261)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$11100(BPlusTree.java:82)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:3143)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7500(BPlusTree.java:2831)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2464)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2185)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7307) H2DynamicIndexingComplexServerTransactionalReplicatedTest.testOperations fails with assertion
[
https://issues.apache.org/jira/browse/IGNITE-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-7307:
---
Labels: mvcc_stabilization_stage_1 transactions (was: transactions)
> H2DynamicIndexingComplexServerTransactionalReplicatedTest.testOperations
> fails with assertion
> -
>
> Key: IGNITE-7307
> URL: https://issues.apache.org/jira/browse/IGNITE-7307
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> {code}
> [2017-12-26 11:40:53,187][ERROR][main][root] Test failed.
> java.lang.AssertionError: localNode = cde0ed21-5bfa-48ee-8e47-53d85880,
> dhtNodes = [TcpDiscoveryNode [id=49318149-4b22-40d1-b68f-8b6b2d52,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47501], discPort=47501, order=3,
> intOrder=3, lastExchangeTime=1514277649002, loc=false,
> ver=2.4.0#19700101-sha1:, isClient=false], TcpDiscoveryNode
> [id=cde0ed21-5bfa-48ee-8e47-53d85880, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1514277652494, loc=true, ver=2.4.0#19700101-sha1:,
> isClient=false], TcpDiscoveryNode [id=7530f231-3bd4-4cc0-b295-0e2f11b3,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=4,
> intOrder=4, lastExchangeTime=1514277649456, loc=false,
> ver=2.4.0#19700101-sha1:, isClient=false]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map(GridDhtTxPrepareFuture.java:1608)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1274)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1056)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsyncLocal(GridNearTxLocal.java:3619)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareColocatedTx(IgniteTxHandler.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.prepareLocal(GridNearPessimisticTxPrepareFuture.java:256)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.preparePessimistic(GridNearPessimisticTxPrepareFuture.java:406)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.prepare(GridNearPessimisticTxPrepareFuture.java:190)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3323)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:3390)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commit(GridNearTxLocal.java:3350)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:429)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:177)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:212)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1809)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1645)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:2034)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:2030)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2527)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:2039)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1995)
> at
> org.apache.ignite.internal.processors.cache.index.H2DynamicIndexingComplexTest.executeSql(H2DynamicIndexingComplexTest.java:333)
> at
>
[jira] [Updated] (IGNITE-7307) H2DynamicIndexingComplexServerTransactionalReplicatedTest.testOperations fails with assertion
[
https://issues.apache.org/jira/browse/IGNITE-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-7307:
---
Labels: H2DynamicIndexingComplexServerTransactionalReplicatedTest.
transactions (was: )
> H2DynamicIndexingComplexServerTransactionalReplicatedTest.testOperations
> fails with assertion
> -
>
> Key: IGNITE-7307
> URL: https://issues.apache.org/jira/browse/IGNITE-7307
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels:
> H2DynamicIndexingComplexServerTransactionalReplicatedTest., transactions
>
> {code}
> [2017-12-26 11:40:53,187][ERROR][main][root] Test failed.
> java.lang.AssertionError: localNode = cde0ed21-5bfa-48ee-8e47-53d85880,
> dhtNodes = [TcpDiscoveryNode [id=49318149-4b22-40d1-b68f-8b6b2d52,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47501], discPort=47501, order=3,
> intOrder=3, lastExchangeTime=1514277649002, loc=false,
> ver=2.4.0#19700101-sha1:, isClient=false], TcpDiscoveryNode
> [id=cde0ed21-5bfa-48ee-8e47-53d85880, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1514277652494, loc=true, ver=2.4.0#19700101-sha1:,
> isClient=false], TcpDiscoveryNode [id=7530f231-3bd4-4cc0-b295-0e2f11b3,
> addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47502], discPort=47502, order=4,
> intOrder=4, lastExchangeTime=1514277649456, loc=false,
> ver=2.4.0#19700101-sha1:, isClient=false]]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.map(GridDhtTxPrepareFuture.java:1608)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1274)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:678)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1056)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareAsyncLocal(GridNearTxLocal.java:3619)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareColocatedTx(IgniteTxHandler.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.prepareLocal(GridNearPessimisticTxPrepareFuture.java:256)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.preparePessimistic(GridNearPessimisticTxPrepareFuture.java:406)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearPessimisticTxPrepareFuture.prepare(GridNearPessimisticTxPrepareFuture.java:190)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.prepareNearTxLocal(GridNearTxLocal.java:3323)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitNearTxLocalAsync(GridNearTxLocal.java:3390)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commit(GridNearTxLocal.java:3350)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:429)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:177)
> at
> org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:212)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1809)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1645)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:2034)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:2030)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2527)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:2039)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1995)
> at
>
[jira] [Updated] (IGNITE-7388) MVCC TX Support async tx rollback on timeout during version requesting.
[ https://issues.apache.org/jira/browse/IGNITE-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-7388: --- Labels: mvcc_stabilization_stage_1 transactions (was: ) > MVCC TX Support async tx rollback on timeout during version requesting. > --- > > Key: IGNITE-7388 > URL: https://issues.apache.org/jira/browse/IGNITE-7388 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Igor Seliverstov >Priority: Major > Labels: mvcc_stabilization_stage_1, transactions > > Currently TX timeout isn't taken into consideration while MVCC version is > requesting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8582) MVCC TX: Cache store read-through support
[
https://issues.apache.org/jira/browse/IGNITE-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-8582:
---
Issue Type: Improvement (was: Bug)
> MVCC TX: Cache store read-through support
> -
>
> Key: IGNITE-8582
> URL: https://issues.apache.org/jira/browse/IGNITE-8582
> Project: Ignite
> Issue Type: Improvement
> Components: mvcc, sql
>Reporter: Sergey Kalashnikov
>Priority: Major
>
> Add support for read-through cache store for mvcc caches.
> Attention should be put on Cache.size method behavior. Cache.size addressed
> in https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
> improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> method (called during load from store) when all existing mvcc row versions
> are aborted or last committed one is _remove_ version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9428) MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
[
https://issues.apache.org/jira/browse/IGNITE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9428:
---
Ignite Flags: (was: Docs Required)
> MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
> --
>
> Key: IGNITE-9428
> URL: https://issues.apache.org/jira/browse/IGNITE-9428
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> Due to IGNITE-9256 patch, multiple {{H2ResultSetIterator#onClose}} invocation
> becomes possible. This can be considered as a {{Closable}} contract violation
> and should be fixed.
> Also this case revealed a bug in {{MvccQueryTrackerImpl}} when multiple
> {{onDone()}} call leads to multiple query finished acks sent back to the
> {{MvccCoordinator}} which leads to the problems with the query tracking and
> assertion errors.
> Reproducer:
> {{CacheMvccSqlTxQueriesAbstractTest#testAccountsTxDmlSumSql_WithRemoves_SingleNode}}
>
>
> Upd: test was fixed in IGNITE-9373. But MvccQueryTrackerImpl.onDone() issue
> is still actual.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9428) MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
[
https://issues.apache.org/jira/browse/IGNITE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9428:
---
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC TX: MvccQueryTrackerImpl.onDone() semantic is broken.
> --
>
> Key: IGNITE-9428
> URL: https://issues.apache.org/jira/browse/IGNITE-9428
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> Due to IGNITE-9256 patch, multiple {{H2ResultSetIterator#onClose}} invocation
> becomes possible. This can be considered as a {{Closable}} contract violation
> and should be fixed.
> Also this case revealed a bug in {{MvccQueryTrackerImpl}} when multiple
> {{onDone()}} call leads to multiple query finished acks sent back to the
> {{MvccCoordinator}} which leads to the problems with the query tracking and
> assertion errors.
> Reproducer:
> {{CacheMvccSqlTxQueriesAbstractTest#testAccountsTxDmlSumSql_WithRemoves_SingleNode}}
>
>
> Upd: test was fixed in IGNITE-9373. But MvccQueryTrackerImpl.onDone() issue
> is still actual.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9605) Implicit mvcc transaction could use completed one instead of starting new
[ https://issues.apache.org/jira/browse/IGNITE-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-9605: --- Labels: mvcc_stabilization_stage_1 transactions (was: ) > Implicit mvcc transaction could use completed one instead of starting new > - > > Key: IGNITE-9605 > URL: https://issues.apache.org/jira/browse/IGNITE-9605 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > Labels: mvcc_stabilization_stage_1, transactions > > It is possible that statement executed outside of explicit transaction uses > completed one explicit transaction from ThreadLocal and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9470) MVCC TX: Mvcc transactions should throw proper exception when rolled back.
[
https://issues.apache.org/jira/browse/IGNITE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9470:
---
Labels: Muted_test mvcc_stabilization_stage_1 transactions (was:
Muted_test)
> MVCC TX: Mvcc transactions should throw proper exception when rolled back.
> --
>
> Key: IGNITE-9470
> URL: https://issues.apache.org/jira/browse/IGNITE-9470
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, mvcc, odbc
>Reporter: Roman Kondakov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: Muted_test, mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> When MVCC transaction is rolled back due to a write conflict it throws
> {{CacheException}} with "Mvcc version mismatch" message. This behavior
> violates Ignite transactions API. Instead it should throw
> {{TransactionRollbackException}} with a clear message like a "Transaction has
> been aborted due to a write conflict (Please try again.)"
> It is also need to propogate this changes to JDBC and ODBC components and fix
> mvcc tests.
>
> In some tests we have to repeat tx operation in case of version conflict.
> Most likely, we can rely to caused-exception with some meaningful type (e.g.
> MvccVersionMismatchException) to repeat operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9927) Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
[
https://issues.apache.org/jira/browse/IGNITE-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9927:
---
Issue Type: Bug (was: Task)
> Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
> ---
>
> Key: IGNITE-9927
> URL: https://issues.apache.org/jira/browse/IGNITE-9927
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> This test was reworked significantly as a part of IGNITE-7953. Unfortunately
> it led to a number of failures appearing from time to time. The goal of this
> ticket is to get rid of these failures.
> Changes from {{51a202a4c48220fa919f47147bd4889033cd35a8}} commit should be
> applied to the test before starting investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9892) MVCC: Exchange hangs on mvcc coordinator fail
[
https://issues.apache.org/jira/browse/IGNITE-9892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9892:
---
Labels: failover mvcc_stabilization_stage_1 (was: )
> MVCC: Exchange hangs on mvcc coordinator fail
> -
>
> Key: IGNITE-9892
> URL: https://issues.apache.org/jira/browse/IGNITE-9892
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Roman Kondakov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> Test
> {{CacheMvccPartitionedSqlCoordinatorFailoverTest#testAccountsTxSql_Server_Backups0_CoordinatorFails}}
> hangs sporadically on exchange.
> Stacktrace:
> {code:java}
> [11:33:18]W: [org.apache.ignite:ignite-indexing] Thread
> [name="exchange-worker-#151671%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest1%",
> id=165981, state=TIMED_WAITING, blockCnt=69, waitCnt=36]
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> sun.misc.Unsafe.park(Native Method)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:219)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:160)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.waitPartitionRelease(GridDhtPartitionsExchangeFuture.java:1433)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1271)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:789)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2657)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2529)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.util.worker.GridWorker.run(GridWorker.java:120)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> java.lang.Thread.run(Thread.java:748)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] Thread
> [name="test-runner-#151510%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest%",
> id=165803, state=RUNNABLE, blockCnt=70, waitCnt=1710]
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> sun.management.ThreadImpl.dumpThreads0(Native Method)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.util.IgniteUtils.dumpThreads(IgniteUtils.java:1356)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:724)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:549)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:533)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest.readWriteTest(CacheMvccAbstractTest.java:1382)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.mvcc.CacheMvccAbstractTest.accountsTxReadAll(CacheMvccAbstractTest.java:773)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.mvcc.CacheMvccAbstractSqlCoordinatorFailoverTest.testAccountsTxSql_Server_Backups0_CoordinatorFails(CacheMvccAbstractSqlCoordinatorFailoverTest.java:35)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [11:33:18]W: [org.apache.ignite:ignite-indexing] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
[jira] [Updated] (IGNITE-10066) Missing key and value constraint validation for MVCC tables
[
https://issues.apache.org/jira/browse/IGNITE-10066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10066:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> Missing key and value constraint validation for MVCC tables
> ---
>
> Key: IGNITE-10066
> URL: https://issues.apache.org/jira/browse/IGNITE-10066
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: PetrovMikhail
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> It seems that key and value constraints for MVCC tables are ignoring now when
> code approach is using to operate with table. The same SQL requests work fine.
> It seems that QueryTypeDescriptorImpl.validateKeyAndValue method call which
> provides corresponding constraints is missed now.
>
> Reproducer for not null constraint:
> {code:java}
> public class IgniteCacheTransactionalSnapshotNullConstraintTest extends
> GridCommonAbstractTest {
> private static final String REPLICATED_CACHE_NAME = "replicatedCacheName";
> private static final String PARTITIONED_CACHE_NAME =
> "partitionedCacheName";
> @Override protected void beforeTestsStarted() throws Exception {
> startGrid(0);
> execSQL("CREATE TABLE table(id INT PRIMARY KEY, str VARCHAR NOT NULL)
> WITH \"atomicity=transactional_snapshot\"");
> jcache(grid(0), cacheConfiguration(REPLICATED,
> TRANSACTIONAL_SNAPSHOT), REPLICATED_CACHE_NAME);
> jcache(grid(0), cacheConfiguration(PARTITIONED,
> TRANSACTIONAL_SNAPSHOT), PARTITIONED_CACHE_NAME);
> }
> protected CacheConfiguration cacheConfiguration(CacheMode cacheMode,
> CacheAtomicityMode atomicityMode) {
> CacheConfiguration cfg = new CacheConfiguration();
> cfg.setCacheMode(cacheMode);
> cfg.setAtomicityMode(atomicityMode);
> cfg.setWriteSynchronizationMode(FULL_SYNC);
> cfg.setQueryEntities(Collections.singletonList(new
> QueryEntity(Integer.class, Person.class)));
> return cfg;
> }
> public void testPutNullValueReplicatedModeFail() throws Exception {
> IgniteCache cache = jcache(0, REPLICATED_CACHE_NAME);
> assertThrowsWithCause(() -> {
> cache.put(0, new Person(null, 25));
> }, IgniteException.class);
> }
> public void testPutNullValuePartitionedModeFail() throws Exception {
> IgniteCache cache = jcache(0,
> PARTITIONED_CACHE_NAME);
> assertThrowsWithCause(() -> {
> cache.put(1, new Person(null, 18));
> }, IgniteException.class);
> }
> public void testPutNullValueSQLFail() throws Exception {
> checkSQLThrows("INSERT INTO table VALUES(?, ?)", NULL_VALUE, 0, null);
> }
> public static class Person implements Serializable {
> @QuerySqlField(notNull = true)
> private String name;
> @QuerySqlField
> private int age;
> public Person(String name, int age) {
> this.name = name;
> this.age = age;
> }
> }
> private void checkSQLThrows(String sql, String sqlStateCode, Object...
> args) {
> IgniteSQLException err =
> (IgniteSQLException)GridTestUtils.assertThrowsWithCause(() -> {
> execSQL(sql, args);
> return 0;
> }, IgniteSQLException.class);
> assertEquals((err).sqlState(), sqlStateCode);
> }
> private List execSQL(String sql, Object... args) {
> SqlFieldsQuery qry = new SqlFieldsQuery(sql)
> .setArgs(args);
> return grid(0).context().query().querySqlFields(qry, true).getAll();
> }
> }
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9927) Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
[
https://issues.apache.org/jira/browse/IGNITE-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9927:
---
Labels: CQ mvcc_stabilization_stage_1 (was: )
> Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
> ---
>
> Key: IGNITE-9927
> URL: https://issues.apache.org/jira/browse/IGNITE-9927
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> This test was reworked significantly as a part of IGNITE-7953. Unfortunately
> it led to a number of failures appearing from time to time. The goal of this
> ticket is to get rid of these failures.
> Changes from {{51a202a4c48220fa919f47147bd4889033cd35a8}} commit should be
> applied to the test before starting investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9927) Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
[
https://issues.apache.org/jira/browse/IGNITE-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9927:
---
Ignite Flags: (was: Docs Required)
> Fix flaky failures in CacheContinuousQueryOperationFromCallbackTest
> ---
>
> Key: IGNITE-9927
> URL: https://issues.apache.org/jira/browse/IGNITE-9927
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: CQ, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> This test was reworked significantly as a part of IGNITE-7953. Unfortunately
> it led to a number of failures appearing from time to time. The goal of this
> ticket is to get rid of these failures.
> Changes from {{51a202a4c48220fa919f47147bd4889033cd35a8}} commit should be
> applied to the test before starting investigation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9949) MVCC TX: Scan query can return wrong result on unstable topology
[
https://issues.apache.org/jira/browse/IGNITE-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-9949:
---
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC TX: Scan query can return wrong result on unstable topology
>
>
> Key: IGNITE-9949
> URL: https://issues.apache.org/jira/browse/IGNITE-9949
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> Scan query map nodes do not take into account topology version when filtering
> primary partitions. See method {{GridCacheQueryManager#scanIterator}} - each
> node takes it's current topology version. This causes wrong partition
> filtering results.
> To fix this problem the single topology version should be taken on reduce
> node propagated to map nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10185) TX can hang forever if any runtime exception occurs on txFinish.
[ https://issues.apache.org/jira/browse/IGNITE-10185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10185: Labels: iep-14 mvcc_stabilization_stage_1 transactions (was: iep-14) > TX can hang forever if any runtime exception occurs on txFinish. > > > Key: IGNITE-10185 > URL: https://issues.apache.org/jira/browse/IGNITE-10185 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Reporter: Andrew Mashenkov >Priority: Major > Labels: iep-14, mvcc_stabilization_stage_1, transactions > > The issue relates to incorrect IOOM handling that can occurs on Tx > prepare\commit\rollback and can be reproduced if persistence enabled and Tx > state logging into WAL enabled. > This affects MVCC tx as it always log it's state into WAL and non-MVCC Tx > with enabled WAL logging via setting IGNITE_WAL_LOG_TX_RECORDS system > property. > We have to check and fix if tx finish methods handle RuntimeExceptions in > proper way. > Good start is to force throw RuntimeException from tm().mvccPrepare() and > tm().mvccFinish() methods, and check if DhtFinishFuture done correctly with > exception rather then (re)throwing exception bypassing failure handler. > The goal is to make IoomFailureHandlerTest passed after runtime failures > during Tx commit\prepare\rollback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10082) MVCC TX: Partition sizes become inconsistent after rebalance.
[ https://issues.apache.org/jira/browse/IGNITE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10082: Labels: failover mvcc_stabilization_stage_1 (was: ) > MVCC TX: Partition sizes become inconsistent after rebalance. > - > > Key: IGNITE-10082 > URL: https://issues.apache.org/jira/browse/IGNITE-10082 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > While rebalance partition size increments on each put operation; since > several versions of one key may be rebalanced, partition sizes become > inconsistent after rebalance finished. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10082) MVCC TX: Partition sizes become inconsistent after rebalance.
[ https://issues.apache.org/jira/browse/IGNITE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10082: Ignite Flags: (was: Docs Required) > MVCC TX: Partition sizes become inconsistent after rebalance. > - > > Key: IGNITE-10082 > URL: https://issues.apache.org/jira/browse/IGNITE-10082 > Project: Ignite > Issue Type: Bug > Components: cache, mvcc >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > While rebalance partition size increments on each put operation; since > several versions of one key may be rebalanced, partition sizes become > inconsistent after rebalance finished. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches
[
https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10104:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC TX: client SFU doesn't work on replicated caches
> -
>
> Key: IGNITE-10104
> URL: https://issues.apache.org/jira/browse/IGNITE-10104
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> When select for update executes from client node the execution is sent to
> random owning node. On that node dht enlist operation is started what causes
> an assertion error because dht enlist operation implies that the node is
> primary for all processed keys.
> see
> {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches
[
https://issues.apache.org/jira/browse/IGNITE-10104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10104:
Ignite Flags: (was: Docs Required)
> MVCC TX: client SFU doesn't work on replicated caches
> -
>
> Key: IGNITE-10104
> URL: https://issues.apache.org/jira/browse/IGNITE-10104
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
> Fix For: 2.8
>
>
> When select for update executes from client node the execution is sent to
> random owning node. On that node dht enlist operation is started what causes
> an assertion error because dht enlist operation implies that the node is
> primary for all processed keys.
> see
> {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10378) MVCC TX: Possible race on MVCC coordinator reassignment
[ https://issues.apache.org/jira/browse/IGNITE-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10378: Labels: failover mvcc_stabilization_stage_1 (was: ) > MVCC TX: Possible race on MVCC coordinator reassignment > --- > > Key: IGNITE-10378 > URL: https://issues.apache.org/jira/browse/IGNITE-10378 > Project: Ignite > Issue Type: Bug > Components: mvcc > Environment: We need to add an additional check to finish MVCC > coordinator init future on particular exchange done only. > >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10359) MVCC: P2P deployment for EntryProcessor looks broken.
[
https://issues.apache.org/jira/browse/IGNITE-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10359:
Ignite Flags: (was: Docs Required)
> MVCC: P2P deployment for EntryProcessor looks broken.
> -
>
> Key: IGNITE-10359
> URL: https://issues.apache.org/jira/browse/IGNITE-10359
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
>
> GridCacheTransactionalEntryProcessorDeploymentSelfTest and
> GridCacheBinaryTransactionalEntryProcessorDeploymentSelfTest fail with
> ClassNotFoundException.
>
>
> {noformat}
> [11:34:44]W: [org.apache.ignite:ignite-core] [2018-11-21
> 08:34:44,810][ERROR][sys-stripe-15-#41929%cache.GridCacheTransactionalEntryProcessorDeploymentSelfTest0%][GridCacheIoManager]
> Failed to
> [11:34:44]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteCheckedException: Failed to send response to node.
> Unsupported direct type [message=GridNearTxEnlistRequest [threadId
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:1043)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:577)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10136)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10188)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridInvokeValue.finishUnmarshal(GridInvokeValue.java:108)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistRequest.finishUnmarshal(GridNearTxEnlistRequest.java:359)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1527)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:574)
> [11:34:44]W: [org.apache.ignite:ignite-core] ... 11 more
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:707)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:704)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1757)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
>
[jira] [Updated] (IGNITE-10183) [Test Failed] IgniteClientReconnectCacheTest.testReconnectOperationInProgress flaky fails on TC.
[
https://issues.apache.org/jira/browse/IGNITE-10183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10183:
Labels: MakeTeamcityGreenAgain failover mvcc_stabilization_stage_1 (was:
MakeTeamcityGreenAgain)
> [Test Failed] IgniteClientReconnectCacheTest.testReconnectOperationInProgress
> flaky fails on TC.
>
>
> Key: IGNITE-10183
> URL: https://issues.apache.org/jira/browse/IGNITE-10183
> Project: Ignite
> Issue Type: Bug
> Components: cache, mvcc
>Affects Versions: 2.7
>Reporter: Pavel Pereslegin
>Priority: Major
> Labels: MakeTeamcityGreenAgain, failover,
> mvcc_stabilization_stage_1
>
> IgniteClientReconnectCacheTest.testReconnectOperationInProgress fails
> sometimes in master (see [recent failures on
> TC|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-1285534571845460301=TEST_STATUS_DESC_IgniteTests24Java8=%3Cdefault%3E=50]).
> Test fails only for cache with {{TRANSACTIONAL_SNAPSHOT}} atomicity mode.
> Typical output:
> {noformat}
> [2018-11-07 23:13:00,579][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteCheckedException: class
> org.apache.ignite.transactions.TransactionRollbackException: Transaction has
> been rolled back: 2e10370f661--0920-4f4e--0026
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7425)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:261)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:191)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkOperationInProgressFails(IgniteClientReconnectCacheTest.java:1421)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectOperationInProgress(IgniteClientReconnectCacheTest.java:869)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2208)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2124)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.transactions.TransactionRollbackException: Transaction has
> been rolled back: 2e10370f661--0920-4f4e--0026
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest$10.apply(IgniteClientReconnectCacheTest.java:834)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest$10.apply(IgniteClientReconnectCacheTest.java:832)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest$25.call(IgniteClientReconnectCacheTest.java:1406)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1003)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1299)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
> Caused by: class org.apache.ignite.transactions.TransactionRollbackException:
> Transaction has been rolled back:
> 2e10370f661--0920-4f4e--0026
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:922)
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:920)
> ... 10 more
> Caused by: class
> org.apache.ignite.internal.transactions.IgniteTxRollbackCheckedException:
> Transaction has been rolled back:
> 2e10370f661--0920-4f4e--0026
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4282)
> at
>
[jira] [Updated] (IGNITE-10241) MVCC TX: orphaned remote transactions
[
https://issues.apache.org/jira/browse/IGNITE-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10241:
Labels: failover mvcc_stabilization_stage_1 (was: )
> MVCC TX: orphaned remote transactions
> -
>
> Key: IGNITE-10241
> URL: https://issues.apache.org/jira/browse/IGNITE-10241
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> {{*CacheMvccPartitionedSqlCoordinatorFailoverTest#testUpdate_N_Objects_ClientServer_Backups2_Sql*
> occasionally fails with following error:}}
> {code:java}
> [2018-11-13
> 15:03:44,240][ERROR][sys-#19392%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest0%][GridDhtPartitionsExchangeFuture]
> Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2@22ae2fbd
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote
> cannot be cast to
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.rollbackMvccTxOnCoordinatorChange(IgniteTxManager.java:327)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onExchangeDone(MvccProcessorImpl.java:394)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2095)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3391)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3157)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2773)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:139)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2578)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2566)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2566)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1747)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:144)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:377)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:335)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3194)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3173)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> at
>
[jira] [Updated] (IGNITE-10219) MVCC: TX: Backup node update may fails after lost tx rollback.
[ https://issues.apache.org/jira/browse/IGNITE-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10219: Labels: mvcc_stabilization_stage_1 transactions (was: ) > MVCC: TX: Backup node update may fails after lost tx rollback. > -- > > Key: IGNITE-10219 > URL: https://issues.apache.org/jira/browse/IGNITE-10219 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > Labels: mvcc_stabilization_stage_1, transactions > Attachments: CacheMvccTxFailoverTest.java > > > The use case: > # Start Tx and update entry. > # Kill backup. > # Rollback Tx (backup miss this tx state change due to outage) > # Start backup. > # Update same entry may fails with unknown tx state for latest entry version. > Backup won't rebalance partition for the key as rollback doesn't increment > partition counter and can't found active transaction for latest entry version > as TxLog contains neither commit nor rollback record. > Also Tx can't be detected as rolled back as mvcc coordinator version hasn't > changed during backup node outage. > > Possible solutions are > # Increment mvcc coordinator version on every node join event that need to > be carefully tested. > # Scan cache to cleanup such entries on node startup (right after recovery > from WAL) which is inefficient. > # Or may be log Tx start in TxLog and rollback all active Tx on node startup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10254) MVCC: invokeAll may hangs on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10254: Labels: Hanging mvcc_stabilization_stage_1 (was: ) > MVCC: invokeAll may hangs on unstable topology. > --- > > Key: IGNITE-10254 > URL: https://issues.apache.org/jira/browse/IGNITE-10254 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > Labels: Hanging, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > Test IgniteCacheEntryProcessorNodeJoinTest.testEntryProcessorNodeLeave() > hangs with TRANSACTIONAL_SNAPSHOT cache mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10359) MVCC: P2P deployment for EntryProcessor looks broken.
[
https://issues.apache.org/jira/browse/IGNITE-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10359:
Labels: mvcc_stabilization_stage_1 transactions (was: deployment
mvcc_stabilization_stage_1)
> MVCC: P2P deployment for EntryProcessor looks broken.
> -
>
> Key: IGNITE-10359
> URL: https://issues.apache.org/jira/browse/IGNITE-10359
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> GridCacheTransactionalEntryProcessorDeploymentSelfTest and
> GridCacheBinaryTransactionalEntryProcessorDeploymentSelfTest fail with
> ClassNotFoundException.
>
>
> {noformat}
> [11:34:44]W: [org.apache.ignite:ignite-core] [2018-11-21
> 08:34:44,810][ERROR][sys-stripe-15-#41929%cache.GridCacheTransactionalEntryProcessorDeploymentSelfTest0%][GridCacheIoManager]
> Failed to
> [11:34:44]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteCheckedException: Failed to send response to node.
> Unsupported direct type [message=GridNearTxEnlistRequest [threadId
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:1043)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:577)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10136)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10188)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridInvokeValue.finishUnmarshal(GridInvokeValue.java:108)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistRequest.finishUnmarshal(GridNearTxEnlistRequest.java:359)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1527)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:574)
> [11:34:44]W: [org.apache.ignite:ignite-core] ... 11 more
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:707)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:704)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
>
[jira] [Updated] (IGNITE-10261) MVCC: cache operation may hangs during late affinity assignment.
[
https://issues.apache.org/jira/browse/IGNITE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10261:
Labels: failover mvcc_stabilization_stage_1 (was: )
> MVCC: cache operation may hangs during late affinity assignment.
>
>
> Key: IGNITE-10261
> URL: https://issues.apache.org/jira/browse/IGNITE-10261
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Andrew Mashenkov
>Assignee: Igor Seliverstov
>Priority: Critical
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> ForceKey response processing fails with ClassCastException with Mvcc mode
> that causes test hanging.
> Issue can be easily reproduced with backups > 0 and disabled rebalance. See
> GridCacheDhtPreloadPutGetSelfTest.testPutGetNone1().
> Also CacheLateAffinityAssignmentTest.testRandomOperations() hangs sometimes
> due to same reason.
>
> {noformat}
> java.lang.ClassCastException:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry
> cannot be cast to
> org.apache.ignite.internal.processors.cache.mvcc.MvccVersionAware
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture$MiniFuture.onResult(GridDhtForceKeysFuture.java:545)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onResult(GridDhtForceKeysFuture.java:202)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processForceKeyResponse(GridDhtCacheAdapter.java:180)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:208)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$11.onMessage(GridDhtTransactionalCacheAdapter.java:206)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1434)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$MessageHandler.apply(GridDhtCacheAdapter.java:1416)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10359) MVCC: P2P deployment for EntryProcessor looks broken.
[
https://issues.apache.org/jira/browse/IGNITE-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10359:
Labels: deployment mvcc_stabilization_stage_1 (was: )
> MVCC: P2P deployment for EntryProcessor looks broken.
> -
>
> Key: IGNITE-10359
> URL: https://issues.apache.org/jira/browse/IGNITE-10359
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: deployment, mvcc_stabilization_stage_1
>
> GridCacheTransactionalEntryProcessorDeploymentSelfTest and
> GridCacheBinaryTransactionalEntryProcessorDeploymentSelfTest fail with
> ClassNotFoundException.
>
>
> {noformat}
> [11:34:44]W: [org.apache.ignite:ignite-core] [2018-11-21
> 08:34:44,810][ERROR][sys-stripe-15-#41929%cache.GridCacheTransactionalEntryProcessorDeploymentSelfTest0%][GridCacheIoManager]
> Failed to
> [11:34:44]W: [org.apache.ignite:ignite-core] class
> org.apache.ignite.IgniteCheckedException: Failed to send response to node.
> Unsupported direct type [message=GridNearTxEnlistRequest [threadId
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:1043)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:577)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> java.lang.Thread.run(Thread.java:748)
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.IgniteCheckedException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10136)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10188)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridInvokeValue.finishUnmarshal(GridInvokeValue.java:108)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistRequest.finishUnmarshal(GridNearTxEnlistRequest.java:359)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1527)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:574)
> [11:34:44]W: [org.apache.ignite:ignite-core] ... 11 more
> [11:34:44]W: [org.apache.ignite:ignite-core] Caused by: class
> org.apache.ignite.binary.BinaryInvalidTypeException:
> org.apache.ignite.tests.p2p.CacheDeploymentBinaryEntryProcessor
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:707)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:704)
> [11:34:44]W: [org.apache.ignite:ignite-core] at
>
[jira] [Updated] (IGNITE-10377) MVCC: Incorrect exception is thrown if no data nodes found for a partition.
[ https://issues.apache.org/jira/browse/IGNITE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10377: Labels: mvcc_stabilization_stage_1 transactions (was: ) > MVCC: Incorrect exception is thrown if no data nodes found for a partition. > --- > > Key: IGNITE-10377 > URL: https://issues.apache.org/jira/browse/IGNITE-10377 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > Labels: mvcc_stabilization_stage_1, transactions > > See NotMappedPartitionInTxTest. > ClusterTopologyServerNotFoundException is expected, instead of > "ClusterTopologyCheckedException: Failed to get primary node" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10378) MVCC TX: Possible race on MVCC coordinator reassignment
[ https://issues.apache.org/jira/browse/IGNITE-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10378: Description: We need to add an additional check to finish MVCC coordinator init future on particular exchange done only. > MVCC TX: Possible race on MVCC coordinator reassignment > --- > > Key: IGNITE-10378 > URL: https://issues.apache.org/jira/browse/IGNITE-10378 > Project: Ignite > Issue Type: Bug > Components: mvcc > Environment: > >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > We need to add an additional check to finish MVCC coordinator init future on > particular exchange done only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10378) MVCC TX: Possible race on MVCC coordinator reassignment
[ https://issues.apache.org/jira/browse/IGNITE-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10378: Ignite Flags: (was: Docs Required) > MVCC TX: Possible race on MVCC coordinator reassignment > --- > > Key: IGNITE-10378 > URL: https://issues.apache.org/jira/browse/IGNITE-10378 > Project: Ignite > Issue Type: Bug > Components: mvcc > Environment: > >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > We need to add an additional check to finish MVCC coordinator init future on > particular exchange done only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10377) MVCC: Incorrect exception is thrown if no data nodes found for a partition.
[ https://issues.apache.org/jira/browse/IGNITE-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10377: Ignite Flags: (was: Docs Required) > MVCC: Incorrect exception is thrown if no data nodes found for a partition. > --- > > Key: IGNITE-10377 > URL: https://issues.apache.org/jira/browse/IGNITE-10377 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Major > > See NotMappedPartitionInTxTest. > ClusterTopologyServerNotFoundException is expected, instead of > "ClusterTopologyCheckedException: Failed to get primary node" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10378) MVCC TX: Possible race on MVCC coordinator reassignment
[ https://issues.apache.org/jira/browse/IGNITE-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10378: Environment: was: We need to add an additional check to finish MVCC coordinator init future on particular exchange done only. > MVCC TX: Possible race on MVCC coordinator reassignment > --- > > Key: IGNITE-10378 > URL: https://issues.apache.org/jira/browse/IGNITE-10378 > Project: Ignite > Issue Type: Bug > Components: mvcc > Environment: > >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Roman Kondakov updated IGNITE-10520: Labels: API mvcc_stabilization_stage_1 (was: ) > 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 >Priority: Critical > Labels: API, mvcc_stabilization_stage_1 > > 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)
[jira] [Updated] (IGNITE-10473) MVCC: Add support for nested system transactions.
[ https://issues.apache.org/jira/browse/IGNITE-10473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10473: Ignite Flags: (was: Docs Required) > MVCC: Add support for nested system transactions. > - > > Key: IGNITE-10473 > URL: https://issues.apache.org/jira/browse/IGNITE-10473 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > Labels: mvcc_stabilization_stage_1, transactions > > IgniteCacheSystemTransactionsSelfTest.testSystemTxInsideUserTx fails in Mvcc > mode due to inner system-tx commits external mvcc-tx unexpectedly. > We have to analyse cases where system tx can be used and deprecated such > cases. > Then we have to either add MVCC support for system caches somehow or allow > non-mvcc nested tx. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10391) MVCC: Invoke request fails on backup while rebalance is in progress.
[ https://issues.apache.org/jira/browse/IGNITE-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10391: Labels: mvcc_stabilization_stage_1 transactions (was: ) > MVCC: Invoke request fails on backup while rebalance is in progress. > > > Key: IGNITE-10391 > URL: https://issues.apache.org/jira/browse/IGNITE-10391 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Critical > Labels: mvcc_stabilization_stage_1, transactions > Fix For: 2.8 > > > Invoke request fails with Assertion on backup while rebalance is in progress. > Enlist request handler expects entry processor instead of value in case of > Invoke operation, > but when rebalance is in progress we pass entry history to backup side. This > causes assertion triggering. > We have to handle correctly this case and apply history and then entry > processor. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10415) MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
[
https://issues.apache.org/jira/browse/IGNITE-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10415:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
>
>
> Key: IGNITE-10415
> URL: https://issues.apache.org/jira/browse/IGNITE-10415
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:816)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:740)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2504)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4323)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2483)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2460)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnIncorrectParamsTest.testLabelFilledLocalGuarantee(TxRollbackOnIncorrectParamsTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2166)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2082)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10415) MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
[
https://issues.apache.org/jira/browse/IGNITE-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10415:
Ignite Flags: (was: Docs Required)
> MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.
>
>
> Key: IGNITE-10415
> URL: https://issues.apache.org/jira/browse/IGNITE-10415
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:660)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:816)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccPutAllAsync0(GridNearTxLocal.java:740)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync0(GridNearTxLocal.java:580)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.putAsync(GridNearTxLocal.java:446)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2504)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$22.op(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4323)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2502)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2483)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2460)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.transactions.TxRollbackOnIncorrectParamsTest.testLabelFilledLocalGuarantee(TxRollbackOnIncorrectParamsTest.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2166)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:144)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2082)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10448) MVCC: NPE on data page eviction.
[
https://issues.apache.org/jira/browse/IGNITE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10448:
Labels: mvcc_stabilization_stage_1 pagememory (was: )
> MVCC: NPE on data page eviction.
>
>
> Key: IGNITE-10448
> URL: https://issues.apache.org/jira/browse/IGNITE-10448
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, pagememory
>
> NPE occurred during page eviction process.
> Reproducer: {{PageEvictionMultinodeMixedRegionsTest}}.
> StackTrace:
>
> {noformat}
> javax.cache.CacheException: class
> org.apache.ignite.transactions.TransactionRollbackException: Transaction has
> been rolled back: 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1108)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.createCacheAndTestEvcition(PageEvictionMultinodeAbstractTest.java:101)
> at
> org.apache.ignite.internal.processors.cache.eviction.paged.PageEvictionMultinodeAbstractTest.testPageEviction(PageEvictionMultinodeAbstractTest.java:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:150)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2104)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2119)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.transactions.TransactionRollbackException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:923)
> at
> org.apache.ignite.internal.util.IgniteUtils$11.apply(IgniteUtils.java:921)
> ... 15 more
> Caused by: class
> org.apache.ignite.internal.transactions.IgniteTxRollbackCheckedException:
> Transaction has been rolled back:
> 83e7f9a5761--093b-7d30--0005
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4299)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put0(GridCacheAdapter.java:2520)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2501)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2478)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1105)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to update
> backup node: [localNodeId=0d817370-17fe-46f1-85ef-ea74b6f1,
> remoteNodeId=ebab34f3-abbc-47e9-90fa-a48a8260]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:1012)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2340)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1200(GridDhtTransactionalCacheAdapter.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:257)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$18.apply(GridDhtTransactionalCacheAdapter.java:255)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1059)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:584)
> at
>
[jira] [Updated] (IGNITE-10434) MVCC: Transaction asynchronous rollback bug.
[
https://issues.apache.org/jira/browse/IGNITE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10434:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC: Transaction asynchronous rollback bug.
>
>
> Key: IGNITE-10434
> URL: https://issues.apache.org/jira/browse/IGNITE-10434
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> There is some bug in mvcc tx asynchronous rollback flow. Sometimes
> transaction is not rolled back completely: Remote transactions remain alive
> while Near and Dht transactions are terminated locally and on MVCC
> coordinator.
> Reproducer: {{MvccTxRollbackAsyncTest#testMixedAsyncRollbackTypes}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10467) MVCC: Failure handling for vacuum threads.
[
https://issues.apache.org/jira/browse/IGNITE-10467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10467:
Issue Type: Improvement (was: Bug)
> MVCC: Failure handling for vacuum threads.
> --
>
> Key: IGNITE-10467
> URL: https://issues.apache.org/jira/browse/IGNITE-10467
> Project: Ignite
> Issue Type: Improvement
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: iep-14
>
> At the moment any critical error in vacuum threads (vacuum-worker,
> vacuum-scheduler) is not handled in any way.
> {{FailureHandler}} implementation should be used to manage such errors. It is
> also need to separate valid cases (partition eviction) from others (page
> corruption, etc.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10455) MVCC: Tx timeout can cause update counters inconsistency.
[
https://issues.apache.org/jira/browse/IGNITE-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10455:
Labels: mvcc_stabilization_stage_1 transactions (was: )
> MVCC: Tx timeout can cause update counters inconsistency.
> --
>
> Key: IGNITE-10455
> URL: https://issues.apache.org/jira/browse/IGNITE-10455
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Igor Seliverstov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, transactions
>
> When transaction is rolled back on backup on prepare step, it could lead to
> update counters inconsistency between primary and backup. We need to fix
> backup counters update.
> Reproducer: {{TxWithSmallTimeoutAndContentionOneKeyTest#test}} with enabled
> MVCC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10470) MVCC: Missed error handling for mvcc transaction updates.
[
https://issues.apache.org/jira/browse/IGNITE-10470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10470:
Labels: iep-14 mvcc_stabilization_stage_1 transactions (was: iep-14)
> MVCC: Missed error handling for mvcc transaction updates.
> -
>
> Key: IGNITE-10470
> URL: https://issues.apache.org/jira/browse/IGNITE-10470
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: iep-14, mvcc_stabilization_stage_1, transactions
>
> Critical errors (page corruption, etc.) during mvcc updates/reads should be
> covered by configured error handler.
> See {{TransactionIntegrityWithPrimaryIndexCorruptionTest}} with enabled mvcc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10474) MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails.
[ https://issues.apache.org/jira/browse/IGNITE-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10474: Ignite Flags: (was: Docs Required) > MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery > fails. > -- > > Key: IGNITE-10474 > URL: https://issues.apache.org/jira/browse/IGNITE-10474 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Roman Kondakov >Priority: Major > Labels: Hanging, mvcc_stabilization_stage_1 > > IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails > due to hanging. > We have to investigate and fix this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10474) MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails.
[ https://issues.apache.org/jira/browse/IGNITE-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10474: Labels: Hanging mvcc_stabilization_stage_1 (was: Hanging) > MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery > fails. > -- > > Key: IGNITE-10474 > URL: https://issues.apache.org/jira/browse/IGNITE-10474 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Roman Kondakov >Priority: Major > Labels: Hanging, mvcc_stabilization_stage_1 > > IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails > due to hanging. > We have to investigate and fix this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10473) MVCC: Add support for nested system transactions.
[ https://issues.apache.org/jira/browse/IGNITE-10473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10473: Labels: mvcc_stabilization_stage_1 transactions (was: ) > MVCC: Add support for nested system transactions. > - > > Key: IGNITE-10473 > URL: https://issues.apache.org/jira/browse/IGNITE-10473 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Minor > Labels: mvcc_stabilization_stage_1, transactions > > IgniteCacheSystemTransactionsSelfTest.testSystemTxInsideUserTx fails in Mvcc > mode due to inner system-tx commits external mvcc-tx unexpectedly. > We have to analyse cases where system tx can be used and deprecated such > cases. > Then we have to either add MVCC support for system caches somehow or allow > non-mvcc nested tx. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Roman Kondakov updated IGNITE-10520: Labels: mvcc_stabilization_stage_1 transactions (was: API mvcc_stabilization_stage_1) > 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 >Priority: Critical > Labels: mvcc_stabilization_stage_1, transactions > > 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)
[jira] [Updated] (IGNITE-10518) MVCC: Update operation may hangs on backup on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10518: Ignite Flags: (was: Docs Required) > MVCC: Update operation may hangs on backup on unstable topology. > - > > Key: IGNITE-10518 > URL: https://issues.apache.org/jira/browse/IGNITE-10518 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Critical > Labels: Hanging, failover, mvcc_stabilization_stage_1 > > Update operation may hangs on backup awaiting next topology. > Symptoms: > # Exchange for topology version 6.1 has been finished. > # Exchange for topology version 6.2 awaits for partition release. > # DhtTxRemote waits for exchange. > Seems, tx maps on outdated topology version. > Reproducer IgniteTxCachePrimarySyncTest.testSingleKeyCommit() in Mvcc mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10518) MVCC: Update operation may hangs on backup on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10518: Labels: Hanging failover mvcc_stabilization_stage_1 (was: failover) > MVCC: Update operation may hangs on backup on unstable topology. > - > > Key: IGNITE-10518 > URL: https://issues.apache.org/jira/browse/IGNITE-10518 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Critical > Labels: Hanging, failover, mvcc_stabilization_stage_1 > > Update operation may hangs on backup awaiting next topology. > Symptoms: > # Exchange for topology version 6.1 has been finished. > # Exchange for topology version 6.2 awaits for partition release. > # DhtTxRemote waits for exchange. > Seems, tx maps on outdated topology version. > Reproducer IgniteTxCachePrimarySyncTest.testSingleKeyCommit() in Mvcc mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10558) MVCC: IgniteWalReader test failed.
[ https://issues.apache.org/jira/browse/IGNITE-10558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10558: Labels: WAL mvcc_stabilization_stage_1 (was: ) > MVCC: IgniteWalReader test failed. > -- > > Key: IGNITE-10558 > URL: https://issues.apache.org/jira/browse/IGNITE-10558 > Project: Ignite > Issue Type: Bug > Components: mvcc, persistence >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: WAL, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > Wal iterator doesn't handle Mvcc wal records. > This causes IgniteWalReader tests failures in Mvcc Pds2 suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10537) MVCC: Client reconnect tests became unstable after mvcc coordinator reassign fix.
[ https://issues.apache.org/jira/browse/IGNITE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10537: Labels: CQ mvcc_stabilization_stage_1 (was: ) > MVCC: Client reconnect tests became unstable after mvcc coordinator reassign > fix. > - > > Key: IGNITE-10537 > URL: https://issues.apache.org/jira/browse/IGNITE-10537 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Roman Kondakov >Assignee: Igor Seliverstov >Priority: Major > Labels: CQ, mvcc_stabilization_stage_1 > > It looks like tests > [CacheMvccContinuousQueryClientReconnectTest.testReconnectClient|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7778544852295951300=testDetails] > and > [CacheMvccContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8370258276605466922=testDetails] > became flaky after commit _5477048 rkondakov on > 22.11.18 at 14:35_. Weshould investigate and fix this problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10551) MVCC: IgniteWalHistoryReservations tests failed.
[ https://issues.apache.org/jira/browse/IGNITE-10551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10551: Labels: WAL mvcc_stabilization_stage_1 (was: WAL) > MVCC: IgniteWalHistoryReservations tests failed. > > > Key: IGNITE-10551 > URL: https://issues.apache.org/jira/browse/IGNITE-10551 > Project: Ignite > Issue Type: Bug > Components: mvcc, persistence >Reporter: Andrew Mashenkov >Priority: Major > Labels: WAL, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > Next tests are failed with MVCC that means we have local-recovery issues: > * IgniteWalHistoryReservationsTest.testNodeIsClearedIfHistoryIsUnavailable > * IgniteWalHistoryReservationsTest.testWalHistoryPartiallyRemoved > Let's investigate and fix this. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10694) MVCC: Possible recycled pages leak.
[
https://issues.apache.org/jira/browse/IGNITE-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10694:
Labels: mvcc_stabilization_stage_1 pagememory (was: memory
mvcc_stabilization_stage_1)
> MVCC: Possible recycled pages leak.
> ---
>
> Key: IGNITE-10694
> URL: https://issues.apache.org/jira/browse/IGNITE-10694
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1, pagememory
>
> Let's consider the following scenario: put N items to cache and then remove
> all these N items. If you repeat this scenario two times, you expect that the
> same number of pages will be recycled each time. But for enabled MVCC this is
> not the case. Reproducers:
> *
> {{PageEvictionPagesRecyclingAndReusingTest#testPagesRecyclingAndReusingMvccTxPartitioned}}
> *
> {{PageEvictionPagesRecyclingAndReusingTest#testPagesRecyclingAndReusingMvccTxReplicated}}
> Perhaps this is because the vacuum does not clean deleted rows completely.
> Detailed investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10693) MVCC TX: Random server restart tests became failed
[ https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10693: Labels: mvcc_stabilization_stage_1 (was: ) > MVCC TX: Random server restart tests became failed > -- > > Key: IGNITE-10693 > URL: https://issues.apache.org/jira/browse/IGNITE-10693 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql >Reporter: Igor Seliverstov >Priority: Major > Labels: mvcc_stabilization_stage_1 > Fix For: 2.8 > > > [one|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7945125576049372508=%3Cdefault%3E=testDetails], > > [two|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8412476034648229784=%3Cdefault%3E=testDetails], > > [three|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=254244004184327163=%3Cdefault%3E=testDetails], > all these tests became failed after IGNITE-9630 has been merged to master. > Seems there is an issue in partition calculating mechanism on unstable > topology. I suppose the algorithm uses partitions on nodes just become > primary while the partitions are in moving state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10518) MVCC: Update operation may hangs on backup on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10518: Labels: failover (was: Failover) > MVCC: Update operation may hangs on backup on unstable topology. > - > > Key: IGNITE-10518 > URL: https://issues.apache.org/jira/browse/IGNITE-10518 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Critical > Labels: failover > > Update operation may hangs on backup awaiting next topology. > Symptoms: > # Exchange for topology version 6.1 has been finished. > # Exchange for topology version 6.2 awaits for partition release. > # DhtTxRemote waits for exchange. > Seems, tx maps on outdated topology version. > Reproducer IgniteTxCachePrimarySyncTest.testSingleKeyCommit() in Mvcc mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10560) MVCC: Data loss after rebalance
[
https://issues.apache.org/jira/browse/IGNITE-10560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10560:
Labels: failover mvcc_stabilization_stage_1 (was: Failover
mvcc_stabilization_stage_1)
> MVCC: Data loss after rebalance
> ---
>
> Key: IGNITE-10560
> URL: https://issues.apache.org/jira/browse/IGNITE-10560
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
>
> It looks like some keys may be lost after cluster rebalance. Reproducer:
> {{GridCacheRebalancingSyncSelfTest#testSimpleRebalancing}} with enabled MVCC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10560) MVCC: Data loss after rebalance
[
https://issues.apache.org/jira/browse/IGNITE-10560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10560:
Labels: Failover mvcc_stabilization_stage_1 (was: Failover)
> MVCC: Data loss after rebalance
> ---
>
> Key: IGNITE-10560
> URL: https://issues.apache.org/jira/browse/IGNITE-10560
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: Failover, mvcc_stabilization_stage_1
>
> It looks like some keys may be lost after cluster rebalance. Reproducer:
> {{GridCacheRebalancingSyncSelfTest#testSimpleRebalancing}} with enabled MVCC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10561) MVCC: Unexpected transaction state after rebalance
[
https://issues.apache.org/jira/browse/IGNITE-10561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10561:
Labels: failover mvcc_stabilization_stage_1 (was: )
> MVCC: Unexpected transaction state after rebalance
> --
>
> Key: IGNITE-10561
> URL: https://issues.apache.org/jira/browse/IGNITE-10561
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
>
> Unexpected transaction state may be observed on some nodes after rebalance.
> Reproducer: {{GridCacheRebalancingSyncSelfTest#testComplexRebalancing}}
> Stacktrace:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Runtime failure on bounds: [lower=MvccSnapshotSearchRow [res=null,
> snapshot=MvccSnapshotResponse [futId=149236, crdVer=1544033736224,
> cntr=800063, opCntr=1073741823, txs=null, cleanupVer=0, tracking=0]],
> upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1756)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.get(IgniteCacheProxyImpl.java:931)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.get(GatewayProtectedCacheProxy.java:640)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingSyncSelfTest.checkData(GridCacheRebalancingSyncSelfTest.java:251)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingSyncSelfTest.checkData(GridCacheRebalancingSyncSelfTest.java:213)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingSyncSelfTest.testComplexRebalancing(GridCacheRebalancingSyncSelfTest.java:588)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccSnapshotSearchRow [res=null, snapshot=MvccSnapshotResponse
> [futId=149236, crdVer=1544033736224, cntr=800063, opCntr=1073741823,
> txs=null, cleanupVer=0, tracking=0]], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.iterate(BPlusTree.java:1035)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccFind(IgniteCacheOffheapManagerImpl.java:2849)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccRead(IgniteCacheOffheapManagerImpl.java:695)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAllAsync0(GridCacheAdapter.java:2024)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.getDhtAllAsync(GridDhtCacheAdapter.java:807)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetSingleFuture.getAsync(GridDhtGetSingleFuture.java:399)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetSingleFuture.map0(GridDhtGetSingleFuture.java:277)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetSingleFuture.map(GridDhtGetSingleFuture.java:259)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtGetSingleFuture.init(GridDhtGetSingleFuture.java:182)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.getDhtSingleAsync(GridDhtCacheAdapter.java:918)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.processNearSingleGetRequest(GridDhtCacheAdapter.java:933)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:152)
> at
>
[jira] [Updated] (IGNITE-10694) MVCC: Possible recycled pages leak.
[
https://issues.apache.org/jira/browse/IGNITE-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10694:
Labels: mvcc_stabilization_stage_1 (was: )
> MVCC: Possible recycled pages leak.
> ---
>
> Key: IGNITE-10694
> URL: https://issues.apache.org/jira/browse/IGNITE-10694
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stabilization_stage_1
>
> Let's consider the following scenario: put N items to cache and then remove
> all these N items. If you repeat this scenario two times, you expect that the
> same number of pages will be recycled each time. But for enabled MVCC this is
> not the case. Reproducers:
> *
> {{PageEvictionPagesRecyclingAndReusingTest#testPagesRecyclingAndReusingMvccTxPartitioned}}
> *
> {{PageEvictionPagesRecyclingAndReusingTest#testPagesRecyclingAndReusingMvccTxReplicated}}
> Perhaps this is because the vacuum does not clean deleted rows completely.
> Detailed investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10582) MVCC: Error on txLog initialization.
[
https://issues.apache.org/jira/browse/IGNITE-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10582:
Labels: Muted_test mvcc_stabilization_stage_1 pagememory (was: Muted_test)
> MVCC: Error on txLog initialization.
>
>
> Key: IGNITE-10582
> URL: https://issues.apache.org/jira/browse/IGNITE-10582
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: Muted_test, mvcc_stabilization_stage_1, pagememory
>
> A sporadic error occurs during {{txLog}} initialization. Reproducer:
> {{IgnitePdsCacheAssignmentNodeRestartsTest#testAssignmentAfterRestarts}}.
> This error may be the result of the test settings. We need to check it more
> carefully.
> Stacktrace:
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> Failed to complete exchange process.
> at
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337)
> at
> org.apache.ignite.internal.IgniteKernal.getOrCreateCaches(IgniteKernal.java:3068)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsCacheAssignmentNodeRestartsTest.testAssignmentAfterRestarts(IgnitePdsCacheAssignmentNodeRestartsTest.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to complete
> exchange process.
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createExchangeException(GridDhtPartitionsExchangeFuture.java:3041)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.sendExchangeFailureMessage(GridDhtPartitionsExchangeFuture.java:3069)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3151)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3135)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2748)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:138)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2556)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2544)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1807)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:145)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:382)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:340)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3294)
> at
>
[jira] [Updated] (IGNITE-10583) MVCC: Assertion on txLog state update when recovering from WAL.
[
https://issues.apache.org/jira/browse/IGNITE-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10583:
Labels: WAL mvcc_stabilization_stage_1 (was: WAL)
> MVCC: Assertion on txLog state update when recovering from WAL.
> ---
>
> Key: IGNITE-10583
> URL: https://issues.apache.org/jira/browse/IGNITE-10583
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: WAL, mvcc_stabilization_stage_1
>
> Assertion in txLog state update occurs sporadically during recovery from WAL.
> Reproducer:
> {{IgnitePdsContinuousRestartTest#testRebalancingDuringLoad_10_10_1_1}} with
> enabled MVCC.
> Stacktrace:
> {noformat}
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on search row: TxKey [major=1544121790766, minor=10468]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1812)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog.put(TxLog.java:245)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.updateState(MvccProcessorImpl.java:609)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLogicalUpdates(GridCacheDatabaseSharedManager.java:2456)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1934)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1050)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:961)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:902)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:890)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:856)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.checkRebalancingDuringLoad(IgnitePdsContinuousRestartTest.java:302)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_10_10_1_1(IgnitePdsContinuousRestartTest.java:221)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: Unexpected new transaction state.
> [currState=2, newState=3, cntr=10468]
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.invalid(TxLog.java:581)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.checkAborted(TxLog.java:562)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:451)
> at
> org.apache.ignite.internal.processors.cache.mvcc.txlog.TxLog$TxLogUpdateClosure.call(TxLog.java:393)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3755)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$5900(BPlusTree.java:3649)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1901)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1779)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10584) MVCC: Wal delta record consistency test failed.
[ https://issues.apache.org/jira/browse/IGNITE-10584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10584: Labels: WAL mvcc_stabilization_stage_1 (was: WAL) > MVCC: Wal delta record consistency test failed. > --- > > Key: IGNITE-10584 > URL: https://issues.apache.org/jira/browse/IGNITE-10584 > Project: Ignite > Issue Type: Bug > Components: mvcc, persistence >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: WAL, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > Next PDS 1 suite tests are failed in Mvcc mode: > CpTriggeredWalDeltaConsistencyTest.testPutRemoveCacheDestroy > ExplicitWalDeltaConsistencyTest.testNotEmptyPds > ExplicitWalDeltaConsistencyTest.testPutRemoveAfterCheckpoint > SysPropWalDeltaConsistencyTest.testPutRemoveMultinode -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10591) MVCC: Incorrect data region metrics.
[
https://issues.apache.org/jira/browse/IGNITE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10591:
Labels: metrics mvcc_stabilization_stage_1 (was: )
> MVCC: Incorrect data region metrics.
>
>
> Key: IGNITE-10591
> URL: https://issues.apache.org/jira/browse/IGNITE-10591
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, persistence
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Labels: metrics, mvcc_stabilization_stage_1
>
> IgnitePdsDataRegionMetricsTest.testMemoryUsageSingleNode failed.
> {noformat}
> junit.framework.AssertionFailedError: Number of allocated pages is different
> than in metrics for [node=db.IgnitePdsDataRegionMetricsTest0, cache=default]
> expected:<13542> but was:<13881>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:159)
> at junit.framework.TestCase.assertEquals(TestCase.java:316)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.IgnitePdsDataRegionMetricsTest.checkMetricsConsistency(IgnitePdsDataRegionMetricsTest.java:337)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.IgnitePdsDataRegionMetricsTest.testMemoryUsageSingleNode(IgnitePdsDataRegionMetricsTest.java:155){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10604) MVCC: IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover fails
[
https://issues.apache.org/jira/browse/IGNITE-10604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10604:
Labels: failover mvcc_stabilization_stage_1 (was: )
> MVCC:
> IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
> fails
>
>
> Key: IGNITE-10604
> URL: https://issues.apache.org/jira/browse/IGNITE-10604
> Project: Ignite
> Issue Type: Bug
> Components: data structures, mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
>
> IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
> fails on closing IgniteAtomicLong datastructure.
> DhtEnlist request with 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)
[jira] [Updated] (IGNITE-10603) MVCC: Inconsistent partition state after recovery.
[
https://issues.apache.org/jira/browse/IGNITE-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10603:
Labels: WAL mvcc_stabilization_stage_1 (was: WAL)
> MVCC: Inconsistent partition state after recovery.
> --
>
> Key: IGNITE-10603
> URL: https://issues.apache.org/jira/browse/IGNITE-10603
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Andrew Mashenkov
>Priority: Major
> Labels: WAL, mvcc_stabilization_stage_1
>
> IgnitePdsPartitionsStateRecoveryTest.testPartitionsStateConsistencyAfterRecoveryNoCheckpoints()
> fails in mvcc mode.
>
> {noformat}
> java.lang.AssertionError: Node restored moving partitions after join to
> topology.
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgnitePdsPartitionsStateRecoveryTest.testPartitionsStateConsistencyAfterRecoveryNoCheckpoints(IgnitePdsPartitionsStateRecoveryTest.java:165)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$001(GridAbstractTest.java:149)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.evaluate(GridAbstractTest.java:2106)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2123)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10693) MVCC TX: Random server restart tests became failed
[ https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10693: Labels: failover mvcc_stabilization_stage_1 (was: mvcc_stabilization_stage_1) > MVCC TX: Random server restart tests became failed > -- > > Key: IGNITE-10693 > URL: https://issues.apache.org/jira/browse/IGNITE-10693 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql >Reporter: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > > [one|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7945125576049372508=%3Cdefault%3E=testDetails], > > [two|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8412476034648229784=%3Cdefault%3E=testDetails], > > [three|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=254244004184327163=%3Cdefault%3E=testDetails], > all these tests became failed after IGNITE-9630 has been merged to master. > Seems there is an issue in partition calculating mechanism on unstable > topology. I suppose the algorithm uses partitions on nodes just become > primary while the partitions are in moving state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10692) MVCC: Test GridCacheDhtPreloadDelayedSelfTest fails in mvcc mode.
[ https://issues.apache.org/jira/browse/IGNITE-10692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kondakov updated IGNITE-10692: Labels: MakeTeamcityGreenAgain mvcc_stabilization_stage_1 (was: MakeTeamcityGreenAgain) > MVCC: Test GridCacheDhtPreloadDelayedSelfTest fails in mvcc mode. > - > > Key: IGNITE-10692 > URL: https://issues.apache.org/jira/browse/IGNITE-10692 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain, mvcc_stabilization_stage_1 > > Next Mvcc Cache 2 suite tests fails on TC with mvcc mode on: > GridCacheDhtPreloadDelayedSelfTest.testAutomaticPreload > GridCacheDhtPreloadDelayedSelfTest.testAutomaticPreloadWithEmptyCache > GridCacheDhtPreloadDelayedSelfTest.testDelayedPreload > > The main issue here GridCommonAbstractTest.dht() method expects nearCache is > configured. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10694) MVCC: Possible recycled pages leak.
[
https://issues.apache.org/jira/browse/IGNITE-10694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-10694:
Labels: memory mvcc_stabilization_stage_1 (was: mvcc_stabilization_stage_1)
> MVCC: Possible recycled pages leak.
> ---
>
> Key: IGNITE-10694
> URL: https://issues.apache.org/jira/browse/IGNITE-10694
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Roman Kondakov
>Priority: Major
> Labels: memory, mvcc_stabilization_stage_1
>
> Let's consider the following scenario: put N items to cache and then remove
> all these N items. If you repeat this scenario two times, you expect that the
> same number of pages will be recycled each time. But for enabled MVCC this is
> not the case. Reproducers:
> *
> {{PageEvictionPagesRecyclingAndReusingTest#testPagesRecyclingAndReusingMvccTxPartitioned}}
> *
> {{PageEvictionPagesRecyclingAndReusingTest#testPagesRecyclingAndReusingMvccTxReplicated}}
> Perhaps this is because the vacuum does not clean deleted rows completely.
> Detailed investigation is needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
