Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
None
Description
Now, Ignite test framework runs tests with multi ignite instances in one JVM.
Need to improve Ignite test framework to have ability run different ignite instances in separate JVMs.
Ideally, it should be isMultiJvm() method, and if isMultiJvm() returns true, then framework will run new grids by startGrid(...) methods in separate JVMs and existng tests have not to be fully rewritten.
Attachments
Issue Links
- incorporates
-
IGNITE-1107 Full Api Milti-JVM testLocalClearKeys test doesn't work for OFFHEAP_TIERED.
- Open
-
IGNITE-1112 Atomic cache #get method returns old value if near cache enabled after second putAll.
- Open
-
IGNITE-1113 GridCacheAtomicNearOnlyMultiJvmFullApiSelfTest.testEvictExpired fails
- Open
-
IGNITE-1104 Need to implement GridCachePartitionedReloadAllAbstractSelfTest in multi-JVM mode.
- Open
-
IGNITE-1105 Need to implement GridCacheAbstractFullApiMultithreadedSelfTest in multi-JVM mode.
- Open
-
IGNITE-1114 Need to implement GridCacheNearTxMultiNodeSelfTest in Multi-JVM mode
- Open
-
IGNITE-1115 Need to implement GridCachePartitionedMultiNodeCounterSelfTest in Multi-JVM mode
- Open
-
IGNITE-1116 Multi JVM unit tests framework should use demon node on local JVM
- Open
-
IGNITE-1117 Implement Cache Failover test in Multi-JVM mode
- Open
-
IGNITE-1088 [Multi jvm] Full api test which test store.
- Closed
-
IGNITE-1089 [Multi jvm] Need to rewrite Full Api ttl tests.
- Closed