[jira] [Created] (IGNITE-11815) Get rid of GridTestUtils.retryAssert method.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11815:
-

 Summary: Get rid of GridTestUtils.retryAssert method.
 Key: IGNITE-11815
 URL: https://issues.apache.org/jira/browse/IGNITE-11815
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


For now we have GridTestUtils.retryAssert() method which runs a closure 'n' 
times to check if some invariantes become ok, eventually.

This method catch assertions and can print them to log many times even if 
assertion is acceptable for the moment.
Also, it is possible to miss an assertion is not related to those ones that 
closure checks  (e.g. assertion error thrown from ignite internals).

 

Let's replace retryAssert with GridTestUtils.waitForCondition() usage.



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

[jira] [Created] (IGNITE-11811) Cache 2 suite test GridCacheDhtPreloadDelayedSelfTest failed on TC.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11811:
-

 Summary: Cache 2 suite test GridCacheDhtPreloadDelayedSelfTest 
failed on TC.
 Key: IGNITE-11811
 URL: https://issues.apache.org/jira/browse/IGNITE-11811
 Project: Ignite
  Issue Type: Test
  Components: cache
Reporter: Andrew Mashenkov


{code:java}
[2019-04-26 08:00:37,500][WARN 
][test-runner-#27151%dht.GridCacheDhtPreloadDelayedSelfTest%][root] Check 
failed (will retry in 500ms).
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheDhtPreloadDelayedSelfTest$5.applyx(GridCacheDhtPreloadDelayedSelfTest.java:465)
at 
org.apache.ignite.internal.util.lang.GridAbsClosureX.apply(GridAbsClosureX.java:34)
at 
org.apache.ignite.testframework.GridTestUtils.retryAssert(GridTestUtils.java:1608)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheDhtPreloadDelayedSelfTest.checkMaps(GridCacheDhtPreloadDelayedSelfTest.java:442)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheDhtPreloadDelayedSelfTest.testDelayedPreload(GridCacheDhtPreloadDelayedSelfTest.java:235)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2044)
at java.lang.Thread.run(Thread.java:748)

{code}



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

[jira] [Created] (IGNITE-11810) Cache2 suite timeouts due to broken IgniteClientCacheStartFailoverTest.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11810:
-

 Summary: Cache2 suite timeouts due to broken 
IgniteClientCacheStartFailoverTest.
 Key: IGNITE-11810
 URL: https://issues.apache.org/jira/browse/IGNITE-11810
 Project: Ignite
  Issue Type: Test
  Components: cache
Reporter: Andrew Mashenkov


{code:java}
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.calculatePartitionUpdateCounters(IgniteTxLocalAdapter.java:492)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userPrepare(IgniteTxLocalAdapter.java:433)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:402)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:569)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:366)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:177)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest(IgniteTxHandler.java:155)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$000(IgniteTxHandler.java:117)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:197)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$1.apply(IgniteTxHandler.java:195)
7][INFO 
][exchange-worker-#71756%cache.IgniteClientCacheStartFailoverTest7%][GridCacheProcessor]
 Started cache [name=tx-1, id=3572520, dataRegionName=null, mode=PARTITIONED, 
atomicity=TRANSACTIONAL, backu
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1140)
6][INFO 
][exchange-worker-#71662%cache.IgniteClientCacheStartFailoverTest5%][GridCacheProcessor]
 Started cache [name=tx-0, id=3572519, dataRegionName=null, mode=PARTITIONED, 
atomicity=TRANSACTIONAL, backu
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:590)
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:1560)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1188)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$8.run(GridIoManager.java:1085)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:549)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)

{code}



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

[jira] [Created] (IGNITE-11686) MVCC: Create separate test for vacuum checks.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11686:
-

 Summary: MVCC: Create separate test for vacuum checks.
 Key: IGNITE-11686
 URL: https://issues.apache.org/jira/browse/IGNITE-11686
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


Most of tests (inherited from CacheMvccAbstractTest) run vacuum synchronously 
on afterTest() method and check if vacuum is ok. This hits performance, can 
cause false negative results and
vacuum issues can be hidden if afterTest method will overriden at once.

For now we have CacheMvccVacuumTest that just check vacuum workers state, but 
there is no check if vacuum really cleans all old versions correctly. I'd 
expect to find it in this class.

So, let's mode vacuum verification from afterTest method into 
CacheMvccVacuumTest as a new separate test.

 



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

[jira] [Created] (IGNITE-11587) MVCC: Remote tx determine its type in wrong way.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11587:
-

 Summary: MVCC: Remote tx determine its type in wrong way. 
 Key: IGNITE-11587
 URL: https://issues.apache.org/jira/browse/IGNITE-11587
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov
 Fix For: 2.8


Remote tx adapters implements IgniteTxState.mvccEnabled in wrong way.
mvccEnabled() checks if writeMap contains a mvcc-entry, but writeMap is always 
empty for mvcc.



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

[jira] [Created] (IGNITE-11559) MVCC: Tx hangs on finish if StorageException occurs.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11559:
-

 Summary: MVCC: Tx hangs on finish if StorageException occurs.
 Key: IGNITE-11559
 URL: https://issues.apache.org/jira/browse/IGNITE-11559
 Project: Ignite
  Issue Type: Bug
  Components: mvcc, persistence
Reporter: Andrew Mashenkov


By default non-mvcc transactions don't log their states in WAL log, so tx 
rollbacks without hanging as there is nothing to save to WAL or PageMemory.
So, it may be helpful to check case for non-mvcc tx with txState WAL-logging 
enabled at first.

When StorageException occurs during any mvcc tx operation enabled, then storage 
locks become blocked. Then Ignite try to rollback Tx due to the error and try 
to save txState into WAL and TxLog and hangs forever. A thread hangs awaiting 
uninterruptibly for next WAL segment or lock released.

Failure handler tries to stop a node and hangs as well.

Looks like we shouldn't wait if kernal context become invalid.

Good startpoint is IgniteWalFlush* tests.



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

[jira] [Created] (IGNITE-11542) Fix flacky test testGivenCacheWithPojoValueAndPds_WhenPut_ThenNoHangup.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11542:
-

 Summary: Fix flacky test 
testGivenCacheWithPojoValueAndPds_WhenPut_ThenNoHangup.
 Key: IGNITE-11542
 URL: https://issues.apache.org/jira/browse/IGNITE-11542
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


IgnitePdsBinarySortObjectFieldsTest.testGivenCacheWithPojoValueAndPds_WhenPut_ThenNoHangup
 fails sporadically on TC due to 5 sec timeout may be not enough for grid 
startup.

Test checks "put" operation will complete in 5 sec timeout, 
but grid initialization is included in this timeout with no reason.



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

[jira] [Created] (IGNITE-11488) GridServiceProcessorBatchDeploySelfTest test fails sporadically

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11488:
-

 Summary: GridServiceProcessorBatchDeploySelfTest test fails 
sporadically
 Key: IGNITE-11488
 URL: https://issues.apache.org/jira/browse/IGNITE-11488
 Project: Ignite
  Issue Type: Test
  Components: managed services
Reporter: Andrew Mashenkov


GridServiceProcessorBatchDeploySelfTest.testCancelAllTopologyChange test fails 
on TC sporadically with ConcurrentModificationException.
Let's add synchronization to certain toString method.

 
{noformat}
 [super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class 
o.a.i.IgniteException: null]]
class org.apache.ignite.IgniteException: null
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl0(GridToStringBuilder.java:1081)
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:993)
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:703)
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:662)
at 
org.apache.ignite.internal.processors.service.ServiceDeploymentTask.toString(ServiceDeploymentTask.java:854)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at 
org.apache.ignite.internal.processors.service.ServiceDeploymentManager$ServicesDeploymentWorker.body(ServiceDeploymentManager.java:502)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
at java.util.HashMap$EntryIterator.next(HashMap.java:1476)
at java.util.HashMap$EntryIterator.next(HashMap.java:1474)
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.addMap(GridToStringBuilder.java:923)
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toString(GridToStringBuilder.java:846)
at 
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl0(GridToStringBuilder.java:1065)
... 9 more{noformat}
 



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

[jira] [Created] (IGNITE-11483) Make system cache non-persistent and deprecate.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11483:
-

 Summary: Make system cache non-persistent and deprecate.
 Key: IGNITE-11483
 URL: https://issues.apache.org/jira/browse/IGNITE-11483
 Project: Ignite
  Issue Type: Bug
  Components: cache, compute, igfs, managed services
Reporter: Andrew Mashenkov


For now, persistent Default Region makes System cache persistent as well (same 
correct for non-persistent region). This behavior is non-obvious and it may 
causes unpredictable issues.

We have number of components that uses system cache, some of them doesn't need 
system cache to be persistent, while other ok with it:
 * DataStructures - datastructures persistence should be configured in it's 
configuration. Moreover, some structures looks broken as 
CacheDataStructureManages uses in-memory maps.
 * Compute - most likely persistence not needed.
 * Services - metastore can be used instead.
 * Igfs - candidate to remove in 3.0

 



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

[jira] [Created] (IGNITE-11466) MVCC: Remove irrelevant tests from mvcc suites.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11466:
-

 Summary: MVCC: Remove irrelevant tests from mvcc suites.
 Key: IGNITE-11466
 URL: https://issues.apache.org/jira/browse/IGNITE-11466
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov
 Fix For: 2.8


For now we have 300+ muted tests related to Mvcc support for LOCAL caches.
As IGNITE-9530 has been closed with "wont fix" we have to
 # Cleanup code and remove test clones like 
IgniteCacheGroupsTest.testCacheIteratorMvccTxLocal
 # Add LOCAL cache test classes to ignore list in Mvcc suites.
 # Other tests should be disabled in Mvcc mode with Assumption and meaningful 
message.
 # All these tests should be unmuted on TC.



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

[jira] [Created] (IGNITE-11462) MVCC: Fix GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11462:
-

 Summary: MVCC: Fix 
GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.
 Key: IGNITE-11462
 URL: https://issues.apache.org/jira/browse/IGNITE-11462
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


Next tests failed on TC:

GridCachePartitionedNearDisabledMvccTxMultiThreadedSelfTest.testPessimisticRepeatableReadCommitMultithreaded

GridCacheReplicatedMvccTxMultiThreadedSelfTest.testPessimisticRepeatableReadCommitMultithreaded

 

Seems, retry on write conflict is missed in test.



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

[jira] [Created] (IGNITE-11420) MVCC: Test fails due to unexpected txRollbackException.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11420:
-

 Summary: MVCC: Test fails due to unexpected txRollbackException.
 Key: IGNITE-11420
 URL: https://issues.apache.org/jira/browse/IGNITE-11420
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


Next tests are failed with unexpected TxRollbackException in mvcc mode:

TxRollbackOnIncorrectParamsTest.testLabelFilledLocalGuarantee
 TxRollbackOnIncorrectParamsTest.testLabelFilledRemoteGuarantee
 
TxRollbackOnIncorrectParamsTest.testRollbackInsideLocalListenerAfterRemoteFilter
 TxRollbackOnIncorrectParamsTest.testTimeoutSetLocalGuarantee
 TxRollbackOnIncorrectParamsTest.testTimeoutSetRemoteGuarantee

Seems, smth was missed in IGNITE-10415 fix or during merge to master.



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

[jira] [Created] (IGNITE-11330) Partition demander should skip entries for invalid partition.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11330:
-

 Summary: Partition demander should skip entries for invalid 
partition.
 Key: IGNITE-11330
 URL: https://issues.apache.org/jira/browse/IGNITE-11330
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Andrew Mashenkov
 Fix For: 2.8


For now Partition demander tries to process all entries for invalid partition 
instead of switching to the next partition.

Looks like, this was introduced with a fix IGNITE-8955 to make checkpoint locks 
fine-grained.
A "for" loop under checkpoint readlock in 
GridDhtPartitionDemander.handleSupplyMessage() causes the issue. A flow can 
breaks inner "for" loop in case of invalid partition, but seems an outer 
"while" loop expected.

 

To resolve this we can e.g. move CacheEntryInfo collection processing into 
separate method and just exit from it if invalid partition is detected.



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

[jira] [Created] (IGNITE-11311) MVCC: SQL full table scan query can return duplicates.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11311:
-

 Summary: MVCC: SQL full table scan query can return duplicates.
 Key: IGNITE-11311
 URL: https://issues.apache.org/jira/browse/IGNITE-11311
 Project: Ignite
  Issue Type: Bug
  Components: mvcc, sql
Reporter: Andrew Mashenkov


SQL query like "select * from table" can return duplicate rows.

Possible reasons can be
 *  due to SQL query iterates over data pages directly and can see inconsistent 
state (IGNITE-10561) 
 * Same as IGNITE-10767, query see stale pages.
 * Smth is wrong with mvcc versions visibility.



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

[jira] [Created] (IGNITE-11247) MVCC: Tests has been forgotten to unmute.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11247:
-

 Summary: MVCC: Tests has been forgotten to unmute.
 Key: IGNITE-11247
 URL: https://issues.apache.org/jira/browse/IGNITE-11247
 Project: Ignite
  Issue Type: New Feature
  Components: mvcc
Reporter: Andrew Mashenkov


There are muted\ignored tests that are not being run on TC, but tickets for 
fixing them looks already resolved.

Let's recheck those tests and either unmute them or create a new tickets to fix 
lately if needed.

IgniteCacheMvccSqlTestSuite
 * testSqlReadInsideTxInProgressCoordinatorFails - IGNITE-8841
 * testSqlReadInsideTxInProgressCoordinatorFails_ReadDelay  - IGNITE-8841

IgniteBasicWithPersistenceTestSuite
 * testIoomErrorMvccPdsHandling - IGNITE-10185

IgniteCacheMvccSqlTestSuite
 * 
testPutAllGetAll_ClientServer_Backups1_SinglePartition_RestartRandomSrv_SqlDml
 * testAccountsTxSql_SingleNode_CoordinatorFails_Persistence

 

 



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

[jira] [Created] (IGNITE-11229) MVCC: Implements chained transactions.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11229:
-

 Summary: MVCC: Implements chained transactions.
 Key: IGNITE-11229
 URL: https://issues.apache.org/jira/browse/IGNITE-11229
 Project: Ignite
  Issue Type: New Feature
  Components: mvcc
Reporter: Andrew Mashenkov


Chained transactions means one executed after another.

To so that we have to add support of combined "COMMIT/BEGIN" command that will 
commits previous transaction and starts a new one. This command should 
guarantee no other transaction allowed in between.

 



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

[jira] [Created] (IGNITE-11228) MVCC: Implement transaction savepoints.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11228:
-

 Summary: MVCC: Implement transaction savepoints.
 Key: IGNITE-11228
 URL: https://issues.apache.org/jira/browse/IGNITE-11228
 Project: Ignite
  Issue Type: New Feature
  Components: mvcc
Reporter: Andrew Mashenkov


Savepoint provides handle for user app to partially rollback a transaction to 
the specific point.

Need to add support for next commands:
"Savepoint" - creates save point with specific identificator (name, label or 
smth like this)

"Rollback to savepoint" - rollback transaction to savepoint.

"Release savepoint" - destroy previously created savepoint.



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

[jira] [Created] (IGNITE-11174) MVCC: Remove deprecated methods form MvccFeatureChecker.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11174:
-

 Summary: MVCC: Remove deprecated methods form MvccFeatureChecker.
 Key: IGNITE-11174
 URL: https://issues.apache.org/jira/browse/IGNITE-11174
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov
 Fix For: 2.8


Let's clean-up the code and remove MvccFeatureChecker.failIfNotSupported method.
MvccFeatureChecker.skipIfNotSupported should be used instead.



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

[jira] [Created] (IGNITE-11170) MVCC: TxLog data region can be cleaned if all mvcc caches gone.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11170:
-

 Summary: MVCC: TxLog data region can be cleaned if all mvcc caches 
gone.
 Key: IGNITE-11170
 URL: https://issues.apache.org/jira/browse/IGNITE-11170
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


Let's clean-up data region if all mvcc caches has been destroyed.



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

[jira] [Created] (IGNITE-11123) MVCC: Fix MvccFeatureChecker to throw assumption exception instead of failure.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11123:
-

 Summary: MVCC: Fix MvccFeatureChecker to throw assumption 
exception instead of failure.
 Key: IGNITE-11123
 URL: https://issues.apache.org/jira/browse/IGNITE-11123
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov
 Fix For: 2.8


Let's rewrite mvcc feature checks with using JUnit4 Assume instead of 
Assert.fail().



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

[jira] [Created] (IGNITE-11090) Test IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupFirstGroup hangs sporadically.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11090:
-

 Summary: Test 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupFirstGroup
 hangs sporadically.
 Key: IGNITE-11090
 URL: https://issues.apache.org/jira/browse/IGNITE-11090
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


[IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupFirstGroup|https://ci.ignite.apache.org/viewLog.html?buildId=2863858=buildResultsDiv=IgniteTests24Java8_Pds4#testNameId7513268742645138398]
 fails sporadically on TC.
{noformat}
[2019-01-21 21:29:28,714][WARN 
][exchange-worker-#58898%rebalancing.IgniteRebalanceOnCachesStoppingOrDestroyingTest1%][diagnostic]
 Latch manager state: ExchangeLatchManager [serverLatches=ConcurrentHashMap {}, 
clientLatches=ConcurrentHashMap {}]
[21:29:29] (err) Failed to notify listener: 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$2...@42d0164ejava.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.WalStateManager.onGroupRebalanceFinished(WalStateManager.java:492)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$2.applyx(GridDhtPartitionDemander.java:298)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$2.applyx(GridDhtPartitionDemander.java:295)
at 
org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:490)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:467)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.checkIsDone(GridDhtPartitionDemander.java:1281)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.checkIsDone(GridDhtPartitionDemander.java:1242)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.partitionDone(GridDhtPartitionDemander.java:1215)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture.access$1100(GridDhtPartitionDemander.java:988)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:803)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:374)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:426)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:416)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1125)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:590)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:108)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1687)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1561)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2753)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1521)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1490)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748){noformat}
[TC 

[jira] [Created] (IGNITE-11088) Flacky LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11088:
-

 Summary: Flacky 
LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge
 Key: IGNITE-11088
 URL: https://issues.apache.org/jira/browse/IGNITE-11088
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


[LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge|https://ci.ignite.apache.org/viewLog.html?buildId=2895774=buildResultsDiv=IgniteTests24Java8_MvccPds2#testNameId-6585115376754732686]
 fails sporadicatlly in MvccPds 2 suite.

I've found no failures in non-mvcc Pds 2 suite, so, probably it is mvcc issue.

See stacktraces from 2 failures that may have same reason. We have to 
investigate this.
{noformat}
java.lang.AssertionError: nodeIdx=2, key=6606 expected:<13212> but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at 
org.apache.ignite.internal.processors.cache.persistence.LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge(LocalWalModeChangeDuringRebalancingSelfTest.java:473)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748) {noformat}
{noformat}
[2019-01-23 
11:26:25,287][ERROR][sys-stripe-5-#6186%persistence.LocalWalModeChangeDuringRebalancingSelfTest3%][GridDhtColocatedCache]
  Failed processing get request: GridNearSingleGetRequest 
[futId=1548243502606, key=KeyCacheObjectImpl [part=381, val=7037, 
hasValBytes=true], flags=1, topVer=AffinityTopologyVersion [topVer=8, 
minorTopVer=1], subjId=f1fbb371-3232-4bfa-a20a-d4cad4b2, taskNameHash=0, 
createTtl=-1, accessTtl=-1, txLbl=null, mvccSnapshot=MvccSnapshotResponse 
[futId=7040, crdVer=1548242747966, cntr=20023, opCntr=1073741823, txs=null, 
cleanupVer=0, tracking=0]] class org.apache.ignite.IgniteCheckedException: 
Runtime failure on bounds: [lower=MvccSnapshotSearchRow [res=null, 
snapshot=MvccSnapshotResponse [futId=7040, crdVer=1548242747966, cntr=20023, 
opCntr=1073741823, txs=null, cleanupVer=0, tracking=0]], upper=MvccMinSearchRow 
[]] at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.iterate(BPlusTree.java:1043)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccFind(IgniteCacheOffheapManagerImpl.java:2683)
 at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccFind(GridCacheOffheapManager.java:2141)
 at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccRead(IgniteCacheOffheapManagerImpl.java:666)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAllAsync0(GridCacheAdapter.java:2023)
 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 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$2.apply(GridDhtTransactionalCacheAdapter.java:150)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1125)
 at 

[jira] [Created] (IGNITE-11085) MVCC: Mute GridCachePartitionEvictionDuringReadThroughSelfTest.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11085:
-

 Summary: MVCC: Mute 
GridCachePartitionEvictionDuringReadThroughSelfTest.
 Key: IGNITE-11085
 URL: https://issues.apache.org/jira/browse/IGNITE-11085
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


There is no need to run GridCachePartitionEvictionDuringReadThroughSelfTest in 
MvccCache 6 suite.

Test uses ATOMIC cache, so we have to either remove it from mvcc run or make it 
use TRANSACTIONAL cache and mute with certain reason as no CacheStore is 
supported in Mvcc mode.

 



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

[jira] [Created] (IGNITE-11082) Test GridCacheDhtTxPreloadSelfTest.testLocalTxPreloadingPessimistic hangs on TC sporadically.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11082:
-

 Summary: Test 
GridCacheDhtTxPreloadSelfTest.testLocalTxPreloadingPessimistic hangs on TC 
sporadically.
 Key: IGNITE-11082
 URL: https://issues.apache.org/jira/browse/IGNITE-11082
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


[GridCacheDhtTxPreloadSelfTest.testLocalTxPreloadingPessimistic|https://ci.ignite.apache.org/viewLog.html?buildId=2899049=buildResultsDiv=IgniteTests24Java8_MvccCache4#testNameId-815824464492790356]
 hanged on TC.

I've saw no failures in non-mvcc 4 cache suite. Probably, the issue relates to 
mvcc.

TC run:
https://ci.ignite.apache.org/viewLog.html?buildId=2899049=buildResultsDiv=IgniteTests24Java8_MvccCache4#testNameId-815824464492790356



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

[jira] [Created] (IGNITE-11081) Flacky test CacheGetReadFromBackupFailoverTest.testFailover

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11081:
-

 Summary: Flacky test 
CacheGetReadFromBackupFailoverTest.testFailover
 Key: IGNITE-11081
 URL: https://issues.apache.org/jira/browse/IGNITE-11081
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


[CacheGetReadFromBackupFailoverTest.testFailover|https://ci.ignite.apache.org/viewLog.html?buildId=2899047=buildResultsDiv=IgniteTests24Java8_MvccCache2#testNameId1077882218748001125]
 fails on TC sporadically.

Smth goes wrong on node stop. At first glance, test is broken.



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

[jira] [Created] (IGNITE-11080) Flacky test GridCacheDhtPreloadDelayedSelfTest.testManualPreload

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11080:
-

 Summary: Flacky test 
GridCacheDhtPreloadDelayedSelfTest.testManualPreload
 Key: IGNITE-11080
 URL: https://issues.apache.org/jira/browse/IGNITE-11080
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


Test is flacky on TC.

Seems, we have to either add ScaleFactor support for those test or rework to 
make it finish in test timeout.



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

[jira] [Created] (IGNITE-11078) MVCC: Tests fails sporadically with ConcurrentModificationException

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11078:
-

 Summary: MVCC: Tests fails sporadically with 
ConcurrentModificationException
 Key: IGNITE-11078
 URL: https://issues.apache.org/jira/browse/IGNITE-11078
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


Next test failed on TC.

[CacheMvccReplicatedSqlCoordinatorFailoverTest.testCoordinatorChangeActiveQueryClientFails_Simple|https://ci.ignite.apache.org/viewLog.html?buildId=2902796=buildResultsDiv=IgniteTests24Java8_MvccQueries#testNameId3071204292938919018]

See TC run for details:

[TC 
run|https://ci.ignite.apache.org/viewLog.html?buildId=2902796=buildResultsDiv=IgniteTests24Java8_MvccQueries#testNameId3071204292938919018]


Stacktrace example:
{code:java}
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
at java.util.HashMap$KeyIterator.next(HashMap.java:1466)
at java.util.AbstractCollection.toString(AbstractCollection.java:461)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at 
java.util.concurrent.ConcurrentHashMap.toString(ConcurrentHashMap.java:1321)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at 
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest$12.apply(CacheMvccAbstractTest.java:1757)
at 
org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1682)
at 
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractTest.checkActiveQueriesCleanup(CacheMvccAbstractTest.java:1750)
at 
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractBasicCoordinatorFailoverTest.checkCoordinatorChangeActiveQueryClientFails_Simple(CacheMvccAbstractBasicCoordinatorFailoverTest.java:689)
at 
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccAbstractSqlCoordinatorFailoverTest.testCoordinatorChangeActiveQueryClientFails_Simple(CacheMvccAbstractSqlCoordinatorFailoverTest.java:164)
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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
at java.lang.Thread.run(Thread.java:748)
{code}
 

 



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

[jira] [Created] (IGNITE-11079) MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11079:
-

 Summary: MVCC: IgniteCacheContinuousQueryBackupQueueTest is flacky.
 Key: IGNITE-11079
 URL: https://issues.apache.org/jira/browse/IGNITE-11079
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


See Tc run
 
[https://ci.ignite.apache.org/viewLog.html?buildId=2859831=buildResultsDiv=IgniteTests24Java8_MvccQueries#testNameId925274886589214180]

Test fails after series of long JVM pauses with stacktrace:
{code:java}
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 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryBackupQueueTest.testManyQueryBackupQueue(IgniteCacheContinuousQueryBackupQueueTest.java:175)
 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.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2088)
 at java.lang.Thread.run(Thread.java:748){code}



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

[jira] [Created] (IGNITE-11067) MVCC: IoStatistics test failed on TC.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11067:
-

 Summary: MVCC: IoStatistics test failed on TC.
 Key: IGNITE-11067
 URL: https://issues.apache.org/jira/browse/IGNITE-11067
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


Next tests failed in MvccCache 9 suite on master:

IoStatisticsCachePersistenceSelfTest.testTransactonalCache 
 IoStatisticsCacheSelfTest.testTransactonalCache 
 IoStatisticsManagerSelfTest.testPersistentIOGlobalStat

Let's exclude these classes from Mvcc suite as they are already contain test 
methods for mvcc mode.



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

[jira] [Created] (IGNITE-11007) MVCC: Potential NPE on non-affinity node for mvcc cache.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11007:
-

 Summary: MVCC: Potential NPE on non-affinity node for mvcc cache.
 Key: IGNITE-11007
 URL: https://issues.apache.org/jira/browse/IGNITE-11007
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


It is possible, non-affinity node (mvcc coordinator or near node) for any mvcc 
cache can try to track tx states and update txLog.

However, txLog may not exists on node if node isn't data node for any mvcc 
cache.



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

[jira] [Created] (IGNITE-11009) TX: TransactionProxyRollbackOnlyImpl throws unexpected exceptions to user.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-11009:
-

 Summary: TX: TransactionProxyRollbackOnlyImpl throws unexpected 
exceptions to user.
 Key: IGNITE-11009
 URL: https://issues.apache.org/jira/browse/IGNITE-11009
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Andrew Mashenkov


TransactionProxyRollbackOnlyImpl can throws  UnsupportedOperationException to 
user.

It is ok if objects throws such exception if someones tries to violate 
contract, 
but seems we use this exceptions in normal flow.
See TxRollbackAsyncTest.testRollbackProxy().

Let's fix implementation to throw correct TransactionException to user.



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

[jira] [Created] (IGNITE-10976) MVCC: Sql API methods should throws proper TransactionExceptions in case of tx failure.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10976:
-

 Summary: MVCC: Sql API methods should throws proper 
TransactionExceptions in case of tx failure.
 Key: IGNITE-10976
 URL: https://issues.apache.org/jira/browse/IGNITE-10976
 Project: Ignite
  Issue Type: Bug
  Components: mvcc, sql
Reporter: Andrew Mashenkov
 Fix For: 2.8


For now Sql API can throws SqlException (without any actual Tx failure cause) 
or TransactionException wrapped into CacheException.

Also, I've found we convert unchecked exceptions into checked ones and then 
back without any obvious reason.

Let's make TransactionException thows properly and add it to Sql Api contract.



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

[jira] [Created] (IGNITE-10969) Add Mvcc tests to RunAll.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10969:
-

 Summary: Add Mvcc tests to RunAll.
 Key: IGNITE-10969
 URL: https://issues.apache.org/jira/browse/IGNITE-10969
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


"Mvcc Cache *" and "Mvcc PDS *" test suites to Run::All suite.



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

[jira] [Created] (IGNITE-10966) MVCC: Add scale factor support in Mvcc tests suites.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10966:
-

 Summary: MVCC: Add scale factor support in Mvcc tests suites.
 Key: IGNITE-10966
 URL: https://issues.apache.org/jira/browse/IGNITE-10966
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


For now, Mvcc suites do not support "scale factor" and run only on nightly 
basis.

We should add "scale factor" for "Mvcc Cache suite" and "Mvcc SQL suite" tests 
to save TC time in RunAll. (Full run on nightly basis with no scaling will not 
be affected)



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

[jira] [Created] (IGNITE-10954) MVCC: Umute fixed tests.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10954:
-

 Summary: MVCC: Umute fixed tests.
 Key: IGNITE-10954
 URL: https://issues.apache.org/jira/browse/IGNITE-10954
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


Check if next tests passes on TC and unmute them,
otherwise re-mute with correct ticket.

IgnitePdsDataRegionMetricsTest.testUsedCheckpointBuffer
TxRollbackAsyncWithPersistenceTest.testSynchronousRollback



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

[jira] [Created] (IGNITE-10871) MVCC: Fix SPI exception handling in mvcc mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10871:
-

 Summary: MVCC: Fix SPI exception handling in mvcc mode.
 Key: IGNITE-10871
 URL: https://issues.apache.org/jira/browse/IGNITE-10871
 Project: Ignite
  Issue Type: Task
  Components: mvcc
Reporter: Andrew Mashenkov


Next tests are failed due to wrong IgniteSpiException handling.

GridCacheReplicatedTxExceptionSelfTest
GridCacheColocatedTxExceptionSelfTest

 

TransactionHeuristicException expected, but CacheException is actually thrown.



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

[jira] [Created] (IGNITE-10863) Fix incorrect links to git repositories.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10863:
-

 Summary: Fix incorrect links to git repositories.
 Key: IGNITE-10863
 URL: https://issues.apache.org/jira/browse/IGNITE-10863
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Andrew Mashenkov
 Fix For: 2.8


We have to refresh outdated links to project git repository.

[https://cwiki.apache.org/confluence/display/IGNITE/] [
https://ignite.apache.org/community/resources.html#git]



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

[jira] [Created] (IGNITE-10822) AbstractFreelist init reused page in wrong way.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10822:
-

 Summary: AbstractFreelist init reused page in wrong way.
 Key: IGNITE-10822
 URL: https://issues.apache.org/jira/browse/IGNITE-10822
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Andrew Mashenkov
 Fix For: 2.8


This is similar to IGNITE-9303.
In IGNITE-9303 we missed wrong page flag check that hides this issue.

After fixing page flag check, one of mvcc tests fails with assertion as Ignite 
can't lock page for write due to unknown reason: smth goes wrong with page tag.

ExplicitWalDeltaConsistencyTest.testNotEmptyPds() fails in mvcc mode with next 
error
{noformat}
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.insertDataRow(AbstractFreeList.java:507)
at 
org.apache.ignite.internal.processors.cache.persistence.metastorage.MetastorageRowStore.addRow(MetastorageRowStore.java:73)
at 
org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.putData(MetaStorage.java:377)
at 
org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.write(MetaStorage.java:353)
at 
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.writeBaselineTopology(GridClusterStateProcessor.java:293)
at 
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onReadyForReadWrite(GridClusterStateProcessor.java:250)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForReadWrite(GridCacheDatabaseSharedManager.java:430)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.finishRecovery(GridCacheDatabaseSharedManager.java:884){noformat}



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

[jira] [Created] (IGNITE-10816) MVCC: create benchmarks for bulk update operations.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10816:
-

 Summary: MVCC: create benchmarks for bulk update operations.
 Key: IGNITE-10816
 URL: https://issues.apache.org/jira/browse/IGNITE-10816
 Project: Ignite
  Issue Type: Bug
  Components: mvcc, sql, yardstick
Reporter: Andrew Mashenkov


For now, we have no any benchmark for bulk update operations (putAll or 
multiple SQL inserts within single transaction)  that can be run in mvcc mode.

1. We should adapt existed PutAllTx benchmarks as they can failed due to write 
conflicts.
2. We should add SQL benchmarks for batched insert\update operations within 
same Tx similar to existed putAll benches.

 



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

[jira] [Created] (IGNITE-10794) MVCC: RemoveAll fails with assertion on unstable topology

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10794:
-

 Summary: MVCC: RemoveAll fails with assertion on unstable topology
 Key: IGNITE-10794
 URL: https://issues.apache.org/jira/browse/IGNITE-10794
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


Looks like partition can change it's state to MOVING.
Reproducer IgniteCacheEntryProcessorNodeJoinTest.testEntryProcessorNodeLeave

See stacktrace:
{noformat}
java.lang.AssertionError: 
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture$Batch.add(GridDhtTxAbstractEnlistFuture.java:1156)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.addToBatch(GridDhtTxAbstractEnlistFuture.java:705)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.processEntry(GridDhtTxAbstractEnlistFuture.java:650)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:533)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:362)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.enlistLocal(GridNearTxEnlistFuture.java:531)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendBatch(GridNearTxEnlistFuture.java:426)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.sendNextBatches(GridNearTxEnlistFuture.java:173)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistFuture.map(GridNearTxEnlistFuture.java:149)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:342)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.init(GridNearTxAbstractEnlistFuture.java:257)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.updateAsync(GridNearTxLocal.java:2074)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.mvccRemoveAllAsync0(GridNearTxLocal.java:1951)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.removeAllAsync0(GridNearTxLocal.java:1670)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.removeAllAsync(GridNearTxLocal.java:550)
{noformat}



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

[jira] [Created] (IGNITE-10759) Disable implicit distributed joins when queryParallelizm>1.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10759:
-

 Summary: Disable implicit distributed joins when 
queryParallelizm>1.
 Key: IGNITE-10759
 URL: https://issues.apache.org/jira/browse/IGNITE-10759
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 1.9
Reporter: Andrew Mashenkov
 Fix For: 2.8


For now, local query with queryParallelizm>1 enables joins between partitions 
on same even if distributedJoins flag is false.

This behaviour is unexpected and can't be disabled.



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

[jira] [Created] (IGNITE-10695) MVCC: Fix cache API conditional update operations.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10695:
-

 Summary: MVCC: Fix cache API conditional update operations.
 Key: IGNITE-10695
 URL: https://issues.apache.org/jira/browse/IGNITE-10695
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Affects Versions: 2.7
Reporter: Andrew Mashenkov
 Fix For: 2.8


Operation like putIfAbsent and replace now tries to transfer Predicate instance 
(filter) to remote node.
 # Almost all filters can't be serialized as they do not have assigned direct 
type.
 # Seems, we have no enough tests and we miss remote-call case for such 
operations.
 # Predicate should be transferred only for "replace" operation if certain 
entry provided, otherwise we should send a correct operation code and use 
corresponding static filter on remote side.
 # This change will break protocol compatibility. Should we bother about it?

Let's fix protocol and add tests.



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

[jira] [Created] (IGNITE-10692) MVCC: Test GridCacheDhtPreloadDelayedSelfTest fails in mvcc mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10692:
-

 Summary: 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


Next 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] [Created] (IGNITE-10662) IgnitePdsDataRegionMetricsTest.testMemoryUsageMultipleNodes fails in TX mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10662:
-

 Summary: 
IgnitePdsDataRegionMetricsTest.testMemoryUsageMultipleNodes fails in TX mode.
 Key: IGNITE-10662
 URL: https://issues.apache.org/jira/browse/IGNITE-10662
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Andrew Mashenkov


IgnitePdsDataRegionMetricsTest.testMemoryUsageMultipleNodes fails with 
TRANSACTIONAL cache.

We should have this test for both Atomic and Tx mode.



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

[jira] [Created] (IGNITE-10652) LocalWalModeNoChangeDuringRebalanceOnNonNodeAssignTest fails on TC

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10652:
-

 Summary: LocalWalModeNoChangeDuringRebalanceOnNonNodeAssignTest 
fails on TC
 Key: IGNITE-10652
 URL: https://issues.apache.org/jira/browse/IGNITE-10652
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Andrew Mashenkov
 Fix For: 2.8


LocalWalModeNoChangeDuringRebalanceOnNonNodeAssignTest fails with TRANSACTIONAL 
cache.

 



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

[jira] [Created] (IGNITE-10637) MVCC: Make diagnostic log messages more informative.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10637:
-

 Summary: MVCC: Make diagnostic log messages more informative.
 Key: IGNITE-10637
 URL: https://issues.apache.org/jira/browse/IGNITE-10637
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


Ignite dumps diagnostic messages with pending objects in case of hanging,
but some information doesn't looks helpful:

Pending mvcc listener:
 >>> o.a.i.i.processors.cache.mvcc.MvccQueryTrackerImpl$ListenerDecorator@261bd7b
 >>> o.a.i.i.processors.cache.mvcc.MvccProcessorImpl$4@6f9e08d4

Let's fix toString methods for these objects to make message more informative.

 



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

[jira] [Created] (IGNITE-10604) MVCC: IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover fails

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10604:
-

 Summary: 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


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] [Created] (IGNITE-10603) MVCC: Inconsistent partition state after recovery.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10603:
-

 Summary: 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


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] [Created] (IGNITE-10591) MVCC: Incorrect data region metrics.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10591:
-

 Summary: 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


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] [Created] (IGNITE-10584) MVCC: Wal delta record consistency test failed.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10584:
-

 Summary: 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






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

[jira] [Created] (IGNITE-10558) MVCC: IgniteWalReader test failed.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10558:
-

 Summary: 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
 Fix For: 2.8


Wal iterator doesn't handle Mvcc wal records.
This causes IgniteWalReader tests failures.



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

[jira] [Created] (IGNITE-10551) MVCC: IgniteWalHistoryReservations tests failed.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10551:
-

 Summary: 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
 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] [Created] (IGNITE-10550) MVCC: rework IgniteWalFlush* tests for mvcc.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10550:
-

 Summary: MVCC: rework IgniteWalFlush* tests for mvcc.
 Key: IGNITE-10550
 URL: https://issues.apache.org/jira/browse/IGNITE-10550
 Project: Ignite
  Issue Type: Test
  Components: mvcc
Reporter: Andrew Mashenkov


Next tests failed in mvcc mode, most likely due to different MVCC tx semantic. 
We have to create similar tests for mvcc mode.

IgniteWalFlushBackgroundSelfTest
IgniteWalFlushBackgroundWithMmapBufferSelfTest
IgniteWalFlushFsyncSelfTest
IgniteWalFlushFsyncWithDedicatedWorkerSelfTest
IgniteWalFlushFsyncWithMmapBufferSelfTest
IgniteWalFlushLogOnlySelfTest
IgniteWalFlushLogOnlyWithMmapBufferSelfTest



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

[jira] [Created] (IGNITE-10526) IgniteWalReaderTest logs too much garbage on node stop.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10526:
-

 Summary: IgniteWalReaderTest logs too much garbage on node stop.
 Key: IGNITE-10526
 URL: https://issues.apache.org/jira/browse/IGNITE-10526
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Andrew Mashenkov


WalIterator log stacktrace for each data record if no cache context found for 
entry.

Let's make it less verbose somehow, e.g. throttle or mock cach context.

 
{noformat}
[18:41:53]W: [org.apache.ignite:ignite-core] [2018-12-04 
15:41:53,626][ERROR][test-runner-#6763%reader.IgniteWalReaderTest%][root] 
Failed to perform post processing for data record
[18:41:53]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.IgniteException: Failed to find cache context for the given 
cache ID: -1368047378
[18:41:53]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.pagemem.wal.record.LazyMvccDataEntry.key(LazyMvccDataEntry.java:97)
[18:41:53]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataEntry(StandaloneWalRecords
[18:41:53]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessDataRecord(StandaloneWalRecord
[18:41:53]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.postProcessRecord(StandaloneWalRecordsIte
[18:41:53]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:248){noformat}
 



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

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

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10520:
-

 Summary: 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
Reporter: Andrew Mashenkov


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] [Created] (IGNITE-10518) MVCC: Update operation may hangs on backup on unstable topology.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10518:
-

 Summary: 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


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] [Created] (IGNITE-10512) Fix javadoc for public Query classes.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10512:
-

 Summary: Fix javadoc for public Query classes.
 Key: IGNITE-10512
 URL: https://issues.apache.org/jira/browse/IGNITE-10512
 Project: Ignite
  Issue Type: Improvement
  Components: documentation, sql
Affects Versions: 1.9
Reporter: Andrew Mashenkov
Assignee: Andrew Mashenkov
 Fix For: 2.8


The documentation for Full TEXT Queries is thin at best:
* What syntax does it use?
* ...is it the full [Lucene Classic Query Parser 
Syntax|https://lucene.apache.org/core/6_3_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html]?
* ...if so how does the syntax map to the {{@QueryTextField}} annotation?
* How is Lucene analyser customisation performed?
* What version is supported? (looks like 3.5.0 which is pretty old, latest is 
6.4.1)
* The 
[{{@QueryTextField}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/annotations/QueryTextField.html]
 JavaDoc refers to 
[{{CacheQuery}}|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/internal/processors/cache/query/CacheQuery.html]
 but strangely this doesn't even appear in the official JavaDoc. It is because 
it's an 'internal' class?

It's mentioned multiple times as a feature, but doesn't look like much of 
Lucene can actually be utilised so clarifications would help greatly.



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

[jira] [Created] (IGNITE-10483) MVCC: Enlist request deserialization failure causes grid hanging.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10483:
-

 Summary: MVCC: Enlist request deserialization failure causes grid 
hanging.
 Key: IGNITE-10483
 URL: https://issues.apache.org/jira/browse/IGNITE-10483
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


Looks like remote serialization issues are not propagated back to near node and 
user request hangs forever.



We should add error handling for all mvcc Enlist requests into 
GridCacheIoManager

 
{noformat}
[19:11:49]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.IgniteCheckedException: Failed to send response to node. 
Unsupported direct type [message=GridNearTxEnlistRequest [threadId
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:1048)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:582)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:383)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:309)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:299)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:505)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
java.lang.Thread.run(Thread.java:748)
[19:11:49]W: [org.apache.ignite:ignite-core] Caused by: class 
org.apache.ignite.IgniteCheckedException: Failed to unmarshal object with 
optimized marshaller
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9997)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10049)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridInvokeValue.finishUnmarshal(GridInvokeValue.java:108)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxEnlistRequest.finishUnmarshal(GridNearTxEnlistRequest.java:359)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1538)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
[19:11:49]W: [org.apache.ignite:ignite-core] ... 11 more
[19:11:49]W: [org.apache.ignite:ignite-core] Caused by: class 
org.apache.ignite.binary.BinaryObjectException: Failed to unmarshal object with 
optimized marshaller
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1789)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1964)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:101)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:81)
[19:11:49]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9991)
[19:11:49]W: 

[jira] [Created] (IGNITE-10476) Merge similar tests.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10476:
-

 Summary: Merge similar tests.
 Key: IGNITE-10476
 URL: https://issues.apache.org/jira/browse/IGNITE-10476
 Project: Ignite
  Issue Type: Test
Reporter: Andrew Mashenkov


CacheNamesSelfTest and CacheNamesWithSpecialCharactersTest looks similar and 
can be merged.

We already have test suite these tests are related to, so we can merge them 
into GridCacheConfigurationValidationSelfTest.

 



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

[jira] [Created] (IGNITE-10474) MVCC: IgniteCacheConnectionRecovery10ConnectionsTest.testConnectionRecovery fails.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10474:
-

 Summary: 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


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] [Created] (IGNITE-10473) MVCC: Add support for nested system transactions.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10473:
-

 Summary: 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


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] [Created] (IGNITE-10472) MVCC: EntryProcessor resource injection missed.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10472:
-

 Summary: MVCC: EntryProcessor resource injection missed.
 Key: IGNITE-10472
 URL: https://issues.apache.org/jira/browse/IGNITE-10472
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


IgniteCacheMvccTxInvokeTest.testInvokeAllAppliedOnceOnBinaryTypeRegistration 
fails with NPE, see stacktrace below.

Seems, we forget to inject resources into EntryProcessor.

 

 
{noformat}
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.IgniteCacheInvokeAbstractTest$2.process(IgniteCacheInvokeAbstractTest.java:345)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.applyEntryProcessor(IgniteCacheOffheapManagerImpl.java:2096)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1998)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:543)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1142)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:463)
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:2064)
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)
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 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:383)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:309)
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:299)
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)
{noformat}
 



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

[jira] [Created] (IGNITE-10466) Test IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse fails sporadically.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10466:
-

 Summary: Test 
IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse fails 
sporadically.
 Key: IGNITE-10466
 URL: https://issues.apache.org/jira/browse/IGNITE-10466
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Andrew Mashenkov


PDS 4 suite fails sporadically on TC when TC is highly loaded.

Looks like there is a connectivity issues on client node after cluster 
activation and before failure. 
But TimeoutProcessor fails on client node with no obvious reason.

 

 
{noformat}
[22:45:44]W: [org.apache.ignite:ignite-core] class 
org.apache.ignite.IgniteException: GridWorker [name=grid-nio-worker-tcp-comm-1, 
igniteInstanceName=client0, finished=false, heartbeatTs=15434
[22:45:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1833)
[22:45:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1828)
[22:45:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
[22:45:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
[22:45:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:221)
[22:45:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
[22:45:44]W: [org.apache.ignite:ignite-core] at 
java.lang.Thread.run(Thread.java:748)
{noformat}
 



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

[jira] [Created] (IGNITE-10465) TTL Worker can fails on node start due to a race.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10465:
-

 Summary: TTL Worker can fails on node start due to a race.
 Key: IGNITE-10465
 URL: https://issues.apache.org/jira/browse/IGNITE-10465
 Project: Ignite
  Issue Type: Bug
  Components: cache, persistence
Reporter: Andrew Mashenkov


PDS 3 suite timeouts sporadicaly on TC if TC is under high load.
Seems, there is a race and TtlWorker starts before node has joined. 

Here is failure dump:
{noformat}
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.getGridStartTime(TcpDiscoverySpi.java:1456)
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.gridStartTime(GridDiscoveryManager.java:2245)
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.version.GridCacheVersionManager.next(GridCacheVersionManager.java:279)
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.version.GridCacheVersionManager.next(GridCacheVersionManager.java:201)
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpiredInternal(GridCacheOffheapM
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.purgeExpired(GridCacheOffheapManager.j
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.expire(GridCacheOffheapManager.java:986)
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:207)
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:141
[17:32:47]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120){noformat}
 

 



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

[jira] [Created] (IGNITE-10460) MVCC: Create "Cache (Failover) 3" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10460:
-

 Summary: MVCC: Create "Cache (Failover) 3" test suite for MVCC 
mode.
 Key: IGNITE-10460
 URL: https://issues.apache.org/jira/browse/IGNITE-10460
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheFailoverTestSuite2 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10464) MVCC: Create "PDS 4" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10464:
-

 Summary: MVCC: Create "PDS 4" test suite for MVCC mode.
 Key: IGNITE-10464
 URL: https://issues.apache.org/jira/browse/IGNITE-10464
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgnitePdsTestSuite3 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10463) MVCC: Create "PDS 3" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10463:
-

 Summary: MVCC: Create "PDS 3" test suite for MVCC mode.
 Key: IGNITE-10463
 URL: https://issues.apache.org/jira/browse/IGNITE-10463
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgnitePdsTestSuite2 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10462) MVCC: Create "PDS 2" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10462:
-

 Summary: MVCC: Create "PDS 2" test suite for MVCC mode.
 Key: IGNITE-10462
 URL: https://issues.apache.org/jira/browse/IGNITE-10462
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgnitePdsTestSuite and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10461) MVCC: Create "PDS 1" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10461:
-

 Summary: MVCC: Create "PDS 1" test suite for MVCC mode.
 Key: IGNITE-10461
 URL: https://issues.apache.org/jira/browse/IGNITE-10461
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheFailoverTestSuite3 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10459) MVCC: Create "Cache (Failover) 2" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10459:
-

 Summary: MVCC: Create "Cache (Failover) 2" test suite for MVCC 
mode.
 Key: IGNITE-10459
 URL: https://issues.apache.org/jira/browse/IGNITE-10459
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheFailoverTestSuite and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10458) MVCC: Create "Cache (Failover) 1" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10458:
-

 Summary: MVCC: Create "Cache (Failover) 1" test suite for MVCC 
mode.
 Key: IGNITE-10458
 URL: https://issues.apache.org/jira/browse/IGNITE-10458
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite9 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10445) Move Tx state to offheap.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10445:
-

 Summary: Move Tx state to offheap.
 Key: IGNITE-10445
 URL: https://issues.apache.org/jira/browse/IGNITE-10445
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Andrew Mashenkov


For now TxManager track tx state in on-heap bounded map structure. Map size can 
be changed with system prop-ty IGNITE_MAX_COMPLETED_TX_COUNT.

Let's move tx structures to offheap like it is done for Mvcc transaction 
(TxLog).

Also seems, we can use tx writeVersion as a commitVersion.

 



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

[jira] [Created] (IGNITE-10444) MVCC: CacheMvccTxFastFinishTest fails.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10444:
-

 Summary: MVCC: CacheMvccTxFastFinishTest fails.
 Key: IGNITE-10444
 URL: https://issues.apache.org/jira/browse/IGNITE-10444
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


Seems, read-only transaction doesn't creates prepare\finish future as classic 
tx do.
Let's check correct invariants in  mvcc version of CacheTxFastFinishTest test.

 



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

[jira] [Created] (IGNITE-10420) Enable ignored test in "Cache 1" test suite.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10420:
-

 Summary: Enable ignored test in "Cache 1" test suite.
 Key: IGNITE-10420
 URL: https://issues.apache.org/jira/browse/IGNITE-10420
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Reporter: Andrew Mashenkov


"Cache 1" TC suite actually runs IgniteBinaryCacheTestSuite.

It looks like we can merge IgniteBinaryCacheTestSuite and IgniteCacheTestSuite 
as the last one is never run separately.

IgniteBinaryCacheTestSuite has ignored test that never run. 
Let's enable these tests and mute them with certain Jira ticket if there is any 
issue.



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

[jira] [Created] (IGNITE-10416) Revisit GridCacheAbstractTest childs.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10416:
-

 Summary: Revisit GridCacheAbstractTest childs.
 Key: IGNITE-10416
 URL: https://issues.apache.org/jira/browse/IGNITE-10416
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Andrew Mashenkov


We have a lot of test inherited from GridCacheAbstractSelfTest, that code is 
complicated and a bit outdated regarding to the fact JUnit 4/5 is coming. 
Moreover,  starting grid from class constructor made test muting tricky and 
disabling cacheStore (which is always enabled by default) doesn't looks 
straightforward in child classes.

 

We should revisit all its childs and check if such parentness is correct.

 

First candidates are:
 # Test has own "start grid routine", but implements gridCount() method just as 
a dummy.
 # Before/After methods do not call parent methods. This should be handled 
carefully.
 # Test that doesn't expect a feature to be used, but enabled in 
GridCacheAbstractSelfTest.
E.g. usually, rebalance test doesn't expect cacheStore to be enabled.



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

[jira] [Created] (IGNITE-10415) MVCC: TxRollbackOnIncorrectParamsTest fails if Mvcc enabled.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10415:
-

 Summary: 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


{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] [Created] (IGNITE-10391) MVCC: Invoke request fails on backup while rebalance is in progress.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10391:
-

 Summary: 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
 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] [Created] (IGNITE-10377) MVCC: Incorrect exception is thrown if no data nodes found for a partition.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10377:
-

 Summary: 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


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] [Created] (IGNITE-10368) MVCC: Create "Cache 9" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10368:
-

 Summary: MVCC: Create "Cache 9" test suite for MVCC mode.
 Key: IGNITE-10368
 URL: https://issues.apache.org/jira/browse/IGNITE-10368
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite8 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10367) MVCC: Create "Cache 8" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10367:
-

 Summary: MVCC: Create "Cache 8" test suite for MVCC mode.
 Key: IGNITE-10367
 URL: https://issues.apache.org/jira/browse/IGNITE-10367
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10366) MVCC: Create "Cache 1" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10366:
-

 Summary: MVCC: Create "Cache 1" test suite for MVCC mode.
 Key: IGNITE-10366
 URL: https://issues.apache.org/jira/browse/IGNITE-10366
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite6 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10365) MVCC: Create "Cache 6" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10365:
-

 Summary: MVCC: Create "Cache 6" test suite for MVCC mode.
 Key: IGNITE-10365
 URL: https://issues.apache.org/jira/browse/IGNITE-10365
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite5 and add it to TC.

All non-relevant tests should be marked as ignored.
Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10362) NoneRebalanceModeSelfTest looks check nothing.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10362:
-

 Summary: NoneRebalanceModeSelfTest looks check nothing.
 Key: IGNITE-10362
 URL: https://issues.apache.org/jira/browse/IGNITE-10362
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrew Mashenkov


Seems, NoneRebalanceModeSelfTest test nothing. It perform next 3 actions:
 # It runs single node and rebalance will never happens regardless rebalance 
mode.
 # It checks partition states, but doesn't if any local partition ever exists
 # It run removeAll without populating cache. And there is no further checks 
anymore.

Let's either drop or refactor NoneRebalanceModeSelfTest.



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

[jira] [Created] (IGNITE-10361) MTCGA: Remove duplicate tests.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10361:
-

 Summary: MTCGA: Remove duplicate tests.
 Key: IGNITE-10361
 URL: https://issues.apache.org/jira/browse/IGNITE-10361
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrew Mashenkov


For now, Cache 3 suite on TC actually starts IgniteBinaryObjectsCacheTestSuite3.
IgniteBinaryObjectsCacheTestSuite3 runs IgniteCacheTestSuite3 in binary mode 
and have 2 additional tests.
- GridCacheBinaryAtomicEntryProcessorDeploymentSelfTest
- GridCacheBinaryTransactionalEntryProcessorDeploymentSelfTest

I've found these additional tests extends ones that are already in 
IgniteCacheTestSuite3, so some tests are run twice.

Possible solution:
1. Exclude non-binary duplicates (from IgniteCacheTestSuite3) from run by 
adding to ignored tests collection.
2. Remove non-binary duplicates and merge binary and non-binary suite into one.

 

 

 



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

[jira] [Created] (IGNITE-10360) MVCC: Refactor MvccUpdateDataRow status handling.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10360:
-

 Summary: MVCC: Refactor MvccUpdateDataRow status handling.
 Key: IGNITE-10360
 URL: https://issues.apache.org/jira/browse/IGNITE-10360
 Project: Ignite
  Issue Type: Improvement
  Components: mvcc
Reporter: Andrew Mashenkov


For now, MvccUpdateDataRow return statuses has unclean names.

E.g. PREV_NULL and PREV_NOT_NULL is about previous value, however FILTERED and 
REMOVED_NOT_NULL is about operation result.

Suggest to replace those result types to e.g.
CREATED, UPDATED, NOOP, REMOVED.



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

[jira] [Created] (IGNITE-10359) MVCC: P2P deployment for EntryProcessor looks broken.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10359:
-

 Summary: 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


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 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
[11:34:44]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
[11:34:44]W: [org.apache.ignite:ignite-core] at 

[jira] [Created] (IGNITE-10345) Discontinue forceServerMode support for client nodes.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10345:
-

 Summary: Discontinue forceServerMode support for client nodes.
 Key: IGNITE-10345
 URL: https://issues.apache.org/jira/browse/IGNITE-10345
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Andrew Mashenkov
 Fix For: 3.0


1. Drop forceServerMode flag from TcpDiscoverySpi. It is already marked as 
deprecated.
2. remove all related tests.



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

[jira] [Created] (IGNITE-10342) TC: Create "Run :: MVCC" suite.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10342:
-

 Summary: TC: Create "Run :: MVCC" suite.
 Key: IGNITE-10342
 URL: https://issues.apache.org/jira/browse/IGNITE-10342
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov
Assignee: Andrew Mashenkov
 Fix For: 2.8


Create MVCC version of IgniteCacheTestSuite3 and add it to TC.

All non-relevant tests should be marked as ignored.
 Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10274) MVCC: Optimize get from local backup.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10274:
-

 Summary: MVCC: Optimize get from local backup.
 Key: IGNITE-10274
 URL: https://issues.apache.org/jira/browse/IGNITE-10274
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Mashenkov


Fix test GridCachePartitionedGetSelfTest.testGetFromBackupNode().

Get from local backup with readFromBackup=true should not create 
SingleGetRequest.



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

[jira] [Created] (IGNITE-10264) MVCC: Enlist request failure on backup can cause grid hanging.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10264:
-

 Summary: MVCC: Enlist request failure on backup can cause grid 
hanging.
 Key: IGNITE-10264
 URL: https://issues.apache.org/jira/browse/IGNITE-10264
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Andrew Mashenkov


See stacktrace below, runtime ClusterTopologyException has not been catched and 
causes transaction hanging.

Seems, we should throws some meaningful checked exception and thow it onto 
primary node.

 
{noformat}
[2018-11-14 
22:26:37,099][ERROR][sys-stripe-3-#10280%cache.IgniteCacheIncrementTxTest7%][GridCacheIoManager]
 Failed to process message [senderId=3774798b-3cbc-4ae1-95d1-745dd371, 
messageType=class 
o.a.i.i.processors.cache.distributed.dht.GridDhtTxQueryFirstEnlistRequest]
 class org.apache.ignite.cluster.ClusterTopologyException: Can not reserve 
partition. Please retry on stable topology.
 at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.mvccEnlistBatch(IgniteTxHandler.java:1865)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistRequest(GridDhtTransactionalCacheAdapter.java:2301)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1100(GridDhtTransactionalCacheAdapter.java:112)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$17.apply(GridDhtTransactionalCacheAdapter.java:250)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$17.apply(GridDhtTransactionalCacheAdapter.java:248)
 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$2$1.run(GridCacheIoManager.java:274)
 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){noformat}
 



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

[jira] [Created] (IGNITE-10263) MVCC: Concurrent cache stop can cause vacuum failure.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10263:
-

 Summary: MVCC: Concurrent cache stop can cause vacuum failure.
 Key: IGNITE-10263
 URL: https://issues.apache.org/jira/browse/IGNITE-10263
 Project: Ignite
  Issue Type: Bug
  Components: cache, mvcc
Reporter: Andrew Mashenkov


The issue can be easily reproduced with IgniteCacheIncrementTxTest in Mvcc mode.

 

Vacuum.cleanup() fails on cctx.gate().enter() if cache is stopped concurrently.

ctx.gate().enter() method fails with IllegalStateException right after readLock 
has been taken.
So, this lock will be never released and prevent writeLock being taken on node 
stop.

Replacing enter() with enterIfNotStopped() resolve the issue, but most likely 
we should release readLock on failure inside gateway.enter().



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

[jira] [Created] (IGNITE-10262) MVCC: Some client operation may hangs if all data nodes leaft the grid.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10262:
-

 Summary: MVCC: Some client operation may hangs if all data nodes 
leaft the grid.
 Key: IGNITE-10262
 URL: https://issues.apache.org/jira/browse/IGNITE-10262
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7
Reporter: Andrew Mashenkov
 Fix For: 2.8


IgniteClientCacheStartFailoverTest.testClientStartLastServerFailsMvccTx() hangs 
forever.

Client put\remove operation should throws CacheServerNotFoundException if there 
is no data server in the grid, but can hangs in some cases.



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

[jira] [Created] (IGNITE-10261) MVCC: Put opearation hangs if rebalance disabled.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10261:
-

 Summary: MVCC: Put opearation hangs if rebalance disabled.
 Key: IGNITE-10261
 URL: https://issues.apache.org/jira/browse/IGNITE-10261
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Mashenkov


ForceKey response processing fails with ClassCastException with Mvcc mode that 
causes test hanging. See GridCacheDhtPreloadPutGetSelfTest.testPutGetNone1()

 

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)



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

[jira] [Created] (IGNITE-10260) MVCC: GetAndPutIfAbsent operation result no result.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10260:
-

 Summary: MVCC: GetAndPutIfAbsent operation result no result.
 Key: IGNITE-10260
 URL: https://issues.apache.org/jira/browse/IGNITE-10260
 Project: Ignite
  Issue Type: Bug
  Components: cache, mvcc
Reporter: Andrew Mashenkov


Next test (but may be not the only) are failed with Mvcc cache mode:

CachePutIfAbsentTest.testTxConflictGetAndPutIfAbsent()
CacheEnumOperationsSingleNodeTest.testMvccTx()



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

[jira] [Created] (IGNITE-10254) MVCC: invokeAll may hangs on unstable topology.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10254:
-

 Summary: 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


Reproduces in 
IgniteCacheEntryProcessorNodeJoinTest.testEntryProcessorNodeLeave()

with TRANSACTIONAL_SNAPSHOT cache mode.



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

[jira] [Created] (IGNITE-10236) MVCC: Create "Cache 3" test suite for MVCC mode.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10236:
-

 Summary: MVCC: Create "Cache 3" test suite for MVCC mode.
 Key: IGNITE-10236
 URL: https://issues.apache.org/jira/browse/IGNITE-10236
 Project: Ignite
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov
Assignee: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite2 and add it to TC.

All non-relevant tests should be marked as ignored.
Failed tests should be muted and tickets should be created for unknown failure 
reasons.



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

[jira] [Created] (IGNITE-10219) MVCC: TX: Backup node update may fails after lost tx rollback.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10219:
-

 Summary: 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


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] [Created] (IGNITE-10185) TX can hang forever if any runtime exception occurs on txFinish.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10185:
-

 Summary: 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
Reporter: Andrew Mashenkov


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] [Created] (IGNITE-10182) Generalize GridInternalSubscriptionProcessor.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10182:
-

 Summary: Generalize GridInternalSubscriptionProcessor.
 Key: IGNITE-10182
 URL: https://issues.apache.org/jira/browse/IGNITE-10182
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrew Mashenkov


For now GridInternalSubscriptionProcessor allows 2 hardcoded types of 
subscribers.
Let's avoid hardcoded types usage.

Suggest to introduce marker interface InternalSubscriber, and export only next 
processor methods.
Register new subscriber: 
 registerSubscriber(InternalSubscriber) 
Notify all subscribers of given type with applying some closure:
  nofitySubscribers(Class, Closure)



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

[jira] [Created] (IGNITE-10187) Partition data can be lost after recover from WAL and no data were ever checkpointed.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-10187:
-

 Summary: Partition data can be lost after recover from WAL and no 
data were ever checkpointed.
 Key: IGNITE-10187
 URL: https://issues.apache.org/jira/browse/IGNITE-10187
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Andrew Mashenkov


Steps to reproduce:
1. Start a node.

2. Disable checkpoints.

3. Put some data.

4. Flush WAL.

5. Restart node.

6. Next put hangs sporadically forever awaiting for next topology that will 
never happens.
The issue caused by ClusterTopologyException thrown due to partition MOVING 
state, however it is expected partition to be in OWNING state.

The root cause is partition doesn't restore OWNING state after recover from WAL 
as it was not checkpointed or contains no data when checkpoint occurs 
(partition was in initial state).

 

Seems, forcing checkpoint before disabling it resolves the issue. See 
CacheMvccTxFailoverTest.testSingleNodeTxMissedCommitNoCheckpoint().

 



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