[jira] [Created] (IGNITE-12072) Starting node with extra cache in cache group cause assertion error
Eduard Shangareev created IGNITE-12072:
--
Summary: Starting node with extra cache in cache group cause
assertion error
Key: IGNITE-12072
URL: https://issues.apache.org/jira/browse/IGNITE-12072
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Reproducer
IgniteCacheGroupsWithRestartsTest#testNodeRestartWithNewStaticallyConfiguredCache
{code}
java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:770)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:747)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2571)
at
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:714)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$beforeExchange$38edadb$1(GridCacheDatabaseSharedManager.java:1415)
at
org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:11037)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12059) DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails
Eduard Shangareev created IGNITE-12059: -- Summary: DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails Key: IGNITE-12059 URL: https://issues.apache.org/jira/browse/IGNITE-12059 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Assignee: Eduard Shangareev DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails because validation was removed in IGNITE-9562. Need to restore this validation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11833) Tests for cache group functionality don't have version with persistence enabled
Eduard Shangareev created IGNITE-11833: -- Summary: Tests for cache group functionality don't have version with persistence enabled Key: IGNITE-11833 URL: https://issues.apache.org/jira/browse/IGNITE-11833 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev There are many tests for cache group functionality but most of them don't have version with enabled persistence. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11780) Command handler refactoring
Eduard Shangareev created IGNITE-11780: -- Summary: Command handler refactoring Key: IGNITE-11780 URL: https://issues.apache.org/jira/browse/IGNITE-11780 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Now it is just a big ball of mud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11728) DELME
Eduard Shangareev created IGNITE-11728: -- Summary: DELME Key: IGNITE-11728 URL: https://issues.apache.org/jira/browse/IGNITE-11728 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Created by mistake -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11606) Index could not contain all values from cache after full rebuild
Eduard Shangareev created IGNITE-11606:
--
Summary: Index could not contain all values from cache after full
rebuild
Key: IGNITE-11606
URL: https://issues.apache.org/jira/browse/IGNITE-11606
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
If index.bin was deleted, we would rebuild it on node start.
But it could cause to the situation when a key is in the cache but SQL query
doesn't return it.
{code}
[18:29:07][:363] idle_verify check has finished, found 1194 conflict
partitions: [counterConflicts=0, hashConflicts=1194]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11579) Add new commands to deal with garbage in partitions which left after cache destroy in shared cache groups
Eduard Shangareev created IGNITE-11579: -- Summary: Add new commands to deal with garbage in partitions which left after cache destroy in shared cache groups Key: IGNITE-11579 URL: https://issues.apache.org/jira/browse/IGNITE-11579 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev The scenario of how to get to this situation (garbage in partition) described in IGNITE-11578. We need to add a new command for control.sh: - show such keys; - remove such keys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11578) Stopping node after destroying cache in shared cache group would leave data of this cache in persistence
Eduard Shangareev created IGNITE-11578: -- Summary: Stopping node after destroying cache in shared cache group would leave data of this cache in persistence Key: IGNITE-11578 URL: https://issues.apache.org/jira/browse/IGNITE-11578 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev If a cache is in a shared group its destroy would trigger async eviction of its cache. If we stop node at the moment, after restart the eviction wouldn't be retriggered. As a result, the part of data of the cache would last on persistence. We could fix it by adding a flag in metastore about eviction start and removing only on eviction stop. If on node start such flag is presented, we need to continue the eviction. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11550) Destroy cache in shared cache group could leave garbage in partitions
Eduard Shangareev created IGNITE-11550: -- Summary: Destroy cache in shared cache group could leave garbage in partitions Key: IGNITE-11550 URL: https://issues.apache.org/jira/browse/IGNITE-11550 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev If the cache was not the only in cache group, cache data would be evicted key by key asynchronously. If the node would go done during the eviction, it wouldn't be continued after restart. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11549) Replace array of AtomicLongs with AtomicLongArray
Eduard Shangareev created IGNITE-11549: -- Summary: Replace array of AtomicLongs with AtomicLongArray Key: IGNITE-11549 URL: https://issues.apache.org/jira/browse/IGNITE-11549 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList#bucketsSize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10931) Get rid of GridTestUtils#addTestIfNeeded
Eduard Shangareev created IGNITE-10931: -- Summary: Get rid of GridTestUtils#addTestIfNeeded Key: IGNITE-10931 URL: https://issues.apache.org/jira/browse/IGNITE-10931 Project: Ignite Issue Type: Task Reporter: Eduard Shangareev It could be replaced with Assume. It will allow to remove some suites with replacing them by new TC configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10880) Document how we should evolve our persistence functionality while keeping it compatible with files created by old versions
Eduard Shangareev created IGNITE-10880: -- Summary: Document how we should evolve our persistence functionality while keeping it compatible with files created by old versions Key: IGNITE-10880 URL: https://issues.apache.org/jira/browse/IGNITE-10880 Project: Ignite Issue Type: Task Components: documentation Reporter: Eduard Shangareev Assignee: Alexey Goncharuk It's not documented at all (???). We need complete documentation to not break compatibility with previously created database files while updating/evolving code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10828) GridAbstractTest wrongly calculates test count
Eduard Shangareev created IGNITE-10828: -- Summary: GridAbstractTest wrongly calculates test count Key: IGNITE-10828 URL: https://issues.apache.org/jira/browse/IGNITE-10828 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev I have found that our naive approach doesn't work. In my case, it counted while 112 while IDEA 113, what cause wrong isLastTest result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10623) Possible JVM crash in case of stopping node with errors
Eduard Shangareev created IGNITE-10623:
--
Summary: Possible JVM crash in case of stopping node with errors
Key: IGNITE-10623
URL: https://issues.apache.org/jira/browse/IGNITE-10623
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
{noformat}
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x03a23bde, pid=5444,
tid=0x18d0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build
1.8.0_102-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode
windows-amd64 compressed oops)
# Problematic frame:
# J 25052 C2
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(IJZ)J
(1421 bytes) @ 0x03a23bde [0x03a23800+0x3de]
#
# Core dump written. Default location:
C:\BuildAgent\work\81a8bed9f07f3feb\ggprivate\hs_err_pid5444.mdmp
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
{noformat}
Seems that it was caused by an erroneous stop on a node which left
checkpoint-thread alive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10478) SQL index creation fails if cache, which query method was called, was statically configured
Eduard Shangareev created IGNITE-10478:
--
Summary: SQL index creation fails if cache, which query method was
called, was statically configured
Key: IGNITE-10478
URL: https://issues.apache.org/jira/browse/IGNITE-10478
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Eduard Shangareev
{code}
javax.cache.CacheException: Cache doesn't exist: cache2
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:698)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:637)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:455)
at
org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotSameTopologyTest.testDynamicIndexForStaticCacheRestoredWithRebuild(IgniteDbSnapshotSameTopologyTest.java:1469)
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:745)
Caused by: class
org.apache.ignite.internal.processors.query.IgniteSQLException: Cache doesn't
exist: cache2
at
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:642)
at
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:242)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFieldsNative(IgniteH2Indexing.java:1661)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1823)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2175)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2170)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2678)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2184)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2204)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2165)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2126)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:686)
... 12 more
{code}
As I see it is thrown from
{code}
if (cache == null || !F.eq(depId, cache.context().dynamicDeploymentId()))
throw new
SchemaOperationException(SchemaOperationException.CODE_CACHE_NOT_FOUND,
cacheName);
{code}
at
org.apache.ignite.internal.processors.query.GridQueryProcessor#processSchemaOperationLocal.
And the second check fails.
It looks strange from my point of view why we throw CODE_CACHE_NOT_FOUND in
this case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10350) Document that now it's allowed to stop caches created via SQL/DDL
Eduard Shangareev created IGNITE-10350: -- Summary: Document that now it's allowed to stop caches created via SQL/DDL Key: IGNITE-10350 URL: https://issues.apache.org/jira/browse/IGNITE-10350 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Eduard Shangareev We need to update our documentation that behavior has changed. https://issues.apache.org/jira/browse/IGNITE-10328 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10328) Allow to destroy cache in code which were created via SQL
Eduard Shangareev created IGNITE-10328:
--
Summary: Allow to destroy cache in code which were created via SQL
Key: IGNITE-10328
URL: https://issues.apache.org/jira/browse/IGNITE-10328
Project: Ignite
Issue Type: Improvement
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
We couldn't destroy cache without using SQL if it was created via SQL.
{code}
Caused by: class org.apache.ignite.IgniteCheckedException: Only cache created
with cache API may be removed with direct call to destroyCache
[cacheName=SQL_PUBLIC_T1]
at
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.processCacheChangeRequests(ClusterCachesInfo.java:677)
at
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.onCacheChangeRequested(ClusterCachesInfo.java:430)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:3827)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:697)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:604)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2667)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2705)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
... 1 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9796) NPE if you call array on empty GridLongList
Eduard Shangareev created IGNITE-9796:
-
Summary: NPE if you call array on empty GridLongList
Key: IGNITE-9796
URL: https://issues.apache.org/jira/browse/IGNITE-9796
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
{code}
/**
*
*/
public void testArray() {
GridLongList list = new GridLongList();
long[] array = list.array();
assertNotNull(array);
assertEquals(0, array.length);
}
{code}
That is it, current version of GridLongList would cause NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9333) Adding page with simple statistic for last 50 runs.
Eduard Shangareev created IGNITE-9333: - Summary: Adding page with simple statistic for last 50 runs. Key: IGNITE-9333 URL: https://issues.apache.org/jira/browse/IGNITE-9333 Project: Ignite Issue Type: Sub-task Reporter: Eduard Shangareev Ok, I am proposing to add a new page which would be named "Statistic". It should show last 50 "Run All" for master, the columns: ||Id||Total tests||Failed tests||Ignored tests|| Muted tests||Total issues (count and the list of TC configurations with links) || Total run time || Also, we need to calculate the statistic. Totals (all unique tests with issues), average issues/fails per run, median, max, min. Total issues = Exit codes + JVM Crashes + OOMs + other issues which caused TC configuration fail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9332) [TC Helper] Add statistic page
Eduard Shangareev created IGNITE-9332: - Summary: [TC Helper] Add statistic page Key: IGNITE-9332 URL: https://issues.apache.org/jira/browse/IGNITE-9332 Project: Ignite Issue Type: Task Reporter: Eduard Shangareev So, we are starting work on adding statistic information to our TC Helper. It should make easier to get an insight into what to do next or what needs to be fixed right now. Also, it should show how we are progressing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9304) AssertionError while updating ATOMIC cache while topology changes
Eduard Shangareev created IGNITE-9304:
-
Summary: AssertionError while updating ATOMIC cache while topology
changes
Key: IGNITE-9304
URL: https://issues.apache.org/jira/browse/IGNITE-9304
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
I have reproduced it with
CacheContinuousQueryFailoverAbstractSelfTest#testMultiThreadedFailover.
{code}
java.lang.AssertionError: Assertion error on search row:
org.apache.ignite.internal.processors.cache.tree.SearchRow@257eba3
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1655)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1306)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:381)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1789)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2471)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1930)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1772)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1662)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3111)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:133)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:269)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:264)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1$2$1.run(GridCacheIoManager.java:275)
at
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:496)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.AssertionError: Invalid version for inner update
[isNew=false, entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=2,
super=GridDistributedCacheEntry [super=CacheObjectImpl [val=null,
hasValBytes=true]CacheObjectImpl [val=null, hasValBytes=true],
ver=GridCacheVersion [topVer=145812931, order=1534332978541, nodeOrder=37],
hash=2, extras=null, flags=0]]], newVer=GridCacheVersion [topVer=145812931,
order=1534332978538, nodeOrder=43]]
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.versionCheck(GridCacheMapEntry.java:5397)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4778)
at
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4562)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3104)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2998)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1744)
at
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1622)
... 20 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9302) Java Thin Clients TC configuration hangs because of no timeout on tests
Eduard Shangareev created IGNITE-9302: - Summary: Java Thin Clients TC configuration hangs because of no timeout on tests Key: IGNITE-9302 URL: https://issues.apache.org/jira/browse/IGNITE-9302 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Assignee: Eduard Shangareev https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JavaThinClient=buildTypeHistoryList_IgniteTests24Java8=__all_branches__ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9266) Cache 2 TC configuration timeouts because of hangs on latch
Eduard Shangareev created IGNITE-9266:
-
Summary: Cache 2 TC configuration timeouts because of hangs on
latch
Key: IGNITE-9266
URL: https://issues.apache.org/jira/browse/IGNITE-9266
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Two threads hanged on waiting latch because of it
GridCacheLocalMultithreadedSelfTest couldn't stop.
{code}
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.171-b11 mixed mode):
"Attach Listener" #2048 daemon prio=9 os_prio=0 tid=0x7f09cc001000
nid=0x6237 waiting on condition [0x]
java.lang.Thread.State: RUNNABLE
"sys-#1820%local.GridCacheLocalMultithreadedSelfTest%" #2047 prio=5 os_prio=0
tid=0x7f089401a000 nid=0x6207 waiting on condition [0x7f09e69ee000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xfad87890> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
"sys-#1819%local.GridCacheLocalMultithreadedSelfTest%" #2046 prio=5 os_prio=0
tid=0x7f0894019000 nid=0x6206 waiting on condition [0x7f09e6aef000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xfad87890> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
"sys-#1818%local.GridCacheLocalMultithreadedSelfTest%" #2045 prio=5 os_prio=0
tid=0x7f0894018000 nid=0x6205 waiting on condition [0x7f09e6bf]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xfad87890> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
"sys-#1817%local.GridCacheLocalMultithreadedSelfTest%" #2044 prio=5 os_prio=0
tid=0x7f0894017000 nid=0x6204 waiting on condition [0x7f09e7ffe000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0xfad87890> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1073)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
"sys-#1816%local.GridCacheLocalMultithreadedSelfTest%" #2043 prio=5 os_prio=0
tid=0x7f0894015800 nid=0x6203 waiting on condition [0x7f09e6ff2000]
java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
[jira] [Created] (IGNITE-9175) AssertionError on simultaneous nodes stop
Eduard Shangareev created IGNITE-9175:
-
Summary: AssertionError on simultaneous nodes stop
Key: IGNITE-9175
URL: https://issues.apache.org/jira/browse/IGNITE-9175
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
{code}
[2018-08-02
20:28:06,639][ERROR][tcp-disco-msg-worker-#6163%grid-tester-3%][TcpDiscoverySpi]
TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node in
order to prevent cluster wide instability.
java.lang.AssertionError
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.sendMessageAcrossRing(ServerImpl.java:2922)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeLeftMessage(ServerImpl.java:4846)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2810)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2604)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7115)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2688)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7059)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9168) AssertionError on local join when coordinator leaves cluster
Eduard Shangareev created IGNITE-9168: - Summary: AssertionError on local join when coordinator leaves cluster Key: IGNITE-9168 URL: https://issues.apache.org/jira/browse/IGNITE-9168 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9159) Basic 2 TC configuration is halted by failure handler
Eduard Shangareev created IGNITE-9159:
-
Summary: Basic 2 TC configuration is halted by failure handler
Key: IGNITE-9159
URL: https://issues.apache.org/jira/browse/IGNITE-9159
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
{code}
[01:19:21][org.apache.ignite:ignite-core] [2018-07-13
22:19:21,713][ERROR][exchange-worker-#3043%messaging.IgniteMessagingConfigVariationFullApiTest3%][IgniteTestResources]
JVM will be halted immediately due to the failure: [failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteCheckedException: Failed
to send message (node may have left the grid or TCP connection cannot be
established due to firewall issues) [node=TcpDiscoveryNode
[id=b8f7b201-ab85-4a14-bcf0-2b397532, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3,
lastExchangeTime=1531520358330, loc=false, ver=2.7.0#20180713-sha1:6a8a2ff8,
isClient=false], topic=TOPIC_CACHE, msg=GridDhtPartitionsSingleMessage
[parts=null, partCntrs=null, partsSizes=null, partHistCntrs=null, err=null,
client=true, compress=true, finishMsg=null,
super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
[topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0],
discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=0fe68fcc-eca6-4f40-9f16-c6181fa0, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1531520358330, loc=false, ver=2.7.0#20180713-sha1:6a8a2ff8,
isClient=false], topVer=10, nodeId8=7b265a8e, msg=Node left: TcpDiscoveryNode
[id=0fe68fcc-eca6-4f40-9f16-c6181fa0, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1531520358330, loc=false, ver=2.7.0#20180713-sha1:6a8a2ff8,
isClient=false], type=NODE_LEFT, tstamp=1531520361620], nodeId=0fe68fcc,
evt=NODE_LEFT], lastVer=GridCacheVersion [topVer=0, order=1531520357089,
nodeOrder=0], super=GridCacheMessage [msgId=238, depInfo=null, err=null,
skipPrepare=false]]], policy=2]]]
[01:19:22][org.apache.ignite:ignite-core] Process exited with code 130
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9142) CacheAsyncOperationsFailoverTxTest hangs because of hanging optimistic transaction
Eduard Shangareev created IGNITE-9142:
-
Summary: CacheAsyncOperationsFailoverTxTest hangs because of
hanging optimistic transaction
Key: IGNITE-9142
URL: https://issues.apache.org/jira/browse/IGNITE-9142
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=1542329&_focus=2400075
{code}
"main" #1 prio=5 os_prio=0 tid=0x7f9ea000d000 nid=0x437d waiting on
condition [0x7f9ea901b000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:816)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.loadData(DataStreamerImpl.java:700)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:666)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.removeDataInternal(DataStreamerImpl.java:619)
at
org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter$GlobalRemoveAllJob.localExecute(GridDistributedCacheAdapter.java:467)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6233)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6744)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1407)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:660)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:532)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:760)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:452)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:408)
at
org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.removeAll(GridDistributedCacheAdapter.java:188)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.removeAll(IgniteCacheProxyImpl.java:1333)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.removeAll(GatewayProtectedCacheProxy.java:1081)
at
org.apache.ignite.internal.processors.cache.GridCacheAbstractSelfTest$1.applyx(GridCacheAbstractSelfTest.java:150)
at
org.apache.ignite.internal.util.lang.GridAbsPredicateX.apply(GridAbsPredicateX.java:32)
at
org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1647)
at
org.apache.ignite.internal.processors.cache.GridCacheAbstractSelfTest.afterTest(GridCacheAbstractSelfTest.java:146)
at
org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1694)
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:503)
at junit.framework.TestCase.runBare(TestCase.java:146)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369)
at
[jira] [Created] (IGNITE-9100) Split Basic and Cache TC configurations on pure in-memory and with disk usage one
Eduard Shangareev created IGNITE-9100: - Summary: Split Basic and Cache TC configurations on pure in-memory and with disk usage one Key: IGNITE-9100 URL: https://issues.apache.org/jira/browse/IGNITE-9100 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Assignee: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9083) Compute (Affinity Run) TC configuration timeouts because of infinite socket operation
Eduard Shangareev created IGNITE-9083:
-
Summary: Compute (Affinity Run) TC configuration timeouts because
of infinite socket operation
Key: IGNITE-9083
URL: https://issues.apache.org/jira/browse/IGNITE-9083
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
https://ci.ignite.apache.org/viewLog.html?buildId=1491175=buildResultsDiv=IgniteTests24Java8_ComputeAffinityRun
https://ci.ignite.apache.org/viewLog.html?buildId=1492399=buildResultsDiv=IgniteTests24Java8_ComputeAffinityRun
{code}
"main" #1 prio=5 os_prio=0 tid=0x7fc29c00d000 nid=0x33e2 runnable
[0x7fc2a31c4000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerInputStreamWrapper.read(JdkMarshallerInputStreamWrapper.java:53)
at
java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2320)
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2333)
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
at java.io.ObjectInputStream.(ObjectInputStream.java:299)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.(JdkMarshallerObjectInputStream.java:43)
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:137)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9939)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.readMessage(TcpDiscoverySpi.java:1729)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1223)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1061)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:905)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:386)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2002)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:916)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1749)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1049)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2020)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1725)
- locked <0xe0ca1e38> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1153)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:651)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:883)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:846)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:834)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:800)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrids(GridAbstractTest.java:684)
at
org.apache.ignite.internal.processors.database.baseline.IgniteBaselineLockPartitionOnAffinityRunTxCacheTest.beforeTest(IgniteBaselineLockPartitionOnAffinityRunTxCacheTest.java:57)
at
org.apache.ignite.testframework.junits.GridAbstractTest.setUp(GridAbstractTest.java:634)
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.setUp(GridCommonAbstractTest.java:490)
at junit.framework.TestCase.runBare(TestCase.java:139)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9081) Allow not-active cluster read metastore
Eduard Shangareev created IGNITE-9081: - Summary: Allow not-active cluster read metastore Key: IGNITE-9081 URL: https://issues.apache.org/jira/browse/IGNITE-9081 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev After IGNITE-9004 we get lock right after node start before activation. Otherwise, we faced with a dirty read of the metastore which cause to assertion errors and so on. But we have forbidden stand-by cluster with this (for example, for quick version update). So we should find a solution to avoid dirty reads of metastore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9080) Activate | Deactivate Cluster is killed by Linux OOM killer
Eduard Shangareev created IGNITE-9080: - Summary: Activate | Deactivate Cluster is killed by Linux OOM killer Key: IGNITE-9080 URL: https://issues.apache.org/jira/browse/IGNITE-9080 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Assignee: Eduard Shangareev As I understand, exit code=137 is about it (kill -9). https://ci.ignite.apache.org/viewLog.html?buildId=1538695=buildResultsDiv=IgniteTests24Java8_ActivateDeactivateCluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9069) Hadoop and IGFS TC configurations fail with exit code = 130
Eduard Shangareev created IGNITE-9069: - Summary: Hadoop and IGFS TC configurations fail with exit code = 130 Key: IGNITE-9069 URL: https://issues.apache.org/jira/browse/IGNITE-9069 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Examples: https://ci.ignite.apache.org/viewLog.html?buildId=1532589=buildResultsDiv=IgniteTests24Java8_Hadoop https://ci.ignite.apache.org/viewLog.html?buildId=1532587=buildResultsDiv=IgniteTests24Java8_IgfsLinuxAndMacOS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9039) AssertionError on cache stop
Eduard Shangareev created IGNITE-9039:
-
Summary: AssertionError on cache stop
Key: IGNITE-9039
URL: https://issues.apache.org/jira/browse/IGNITE-9039
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
It was introduced by IGNITE-8955:
{code}
[2018-07-20 13:24:39,190][INFO
][exchange-worker-#38%db.CheckpointBufferDeadlockTest0%][root]
[GridStringLogger echo] class org.apache.ignite.IgniteCheckedException:
Compound exception for CountDownFuture. at
org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
at
org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
at
org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$ClearSegmentRunnable.run(PageMemoryImpl.java:2757)
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)
Suppressed: java.lang.AssertionError: Release pinned page: FullPageId
[pageId=00013c43, effectivePageId=3c43, grpId=-1778028968]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.releaseFreePage(PageMemoryImpl.java:1787)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.access$1900(PageMemoryImpl.java:1659)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$ClearSegmentRunnable.run(PageMemoryImpl.java:2748)
... 3 more
Suppressed: java.lang.AssertionError: Release pinned page: FullPageId
[pageId=000128bc, effectivePageId=28bc, grpId=-1778028968]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.releaseFreePage(PageMemoryImpl.java:1787)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.access$1900(PageMemoryImpl.java:1659)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$ClearSegmentRunnable.run(PageMemoryImpl.java:2748)
... 3 more
Suppressed: java.lang.AssertionError: Release pinned page: FullPageId
[pageId=00013f1a, effectivePageId=3f1a, grpId=-1778028968]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.releaseFreePage(PageMemoryImpl.java:1787)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.access$1900(PageMemoryImpl.java:1659)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$ClearSegmentRunnable.run(PageMemoryImpl.java:2748)
... 3 more
Suppressed: java.lang.AssertionError: Release pinned page: FullPageId
[pageId=00012eb9, effectivePageId=2eb9, grpId=-1778028968]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.releaseFreePage(PageMemoryImpl.java:1787)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.access$1900(PageMemoryImpl.java:1659)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$ClearSegmentRunnable.run(PageMemoryImpl.java:2748)
... 3 more
Suppressed: java.lang.AssertionError: Release pinned page: FullPageId
[pageId=000120f2, effectivePageId=20f2, grpId=-1778028968]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.releaseFreePage(PageMemoryImpl.java:1787)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.access$1900(PageMemoryImpl.java:1659)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$ClearSegmentRunnable.run(PageMemoryImpl.java:2748)
... 3 more
Suppressed: java.lang.AssertionError: Release pinned page: FullPageId
[pageId=000115e9, effectivePageId=15e9, grpId=-1778028968]
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$PagePool.releaseFreePage(PageMemoryImpl.java:1787)
at
[jira] [Created] (IGNITE-9025) "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest
Eduard Shangareev created IGNITE-9025: - Summary: "PDS 1" TC configuration could hang because of SegmentedRingByteBufferTest Key: IGNITE-9025 URL: https://issues.apache.org/jira/browse/IGNITE-9025 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9018) PDS1 TC configuration hangs periodically
Eduard Shangareev created IGNITE-9018:
-
Summary: PDS1 TC configuration hangs periodically
Key: IGNITE-9018
URL: https://issues.apache.org/jira/browse/IGNITE-9018
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
At least one timeout was caused by next
{code} "main" #1 prio=5 os_prio=0 tid=0x7ff12000e000 nid=0xeaa waiting on
condition [0x7ff12694e000] java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method) at
org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7658) at
org.apache.ignite.internal.processors.cache.persistence.wal.SegmentedRingByteBufferTest.doTestNoOverflowMultiThreaded(SegmentedRingByteBufferTest.java:375)
at
org.apache.ignite.internal.processors.cache.persistence.wal.SegmentedRingByteBufferTest.testNoOverflowMultiThreaded(SegmentedRingByteBufferTest.java:79)
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
junit.framework.TestCase.runBare(TestCase.java:141) at
junit.framework.TestResult$1.protect(TestResult.java:122) at
junit.framework.TestResult.runProtected(TestResult.java:142) at
junit.framework.TestResult.run(TestResult.java:125) at
junit.framework.TestCase.run(TestCase.java:129) at
junit.framework.TestSuite.runTest(TestSuite.java:255) at
junit.framework.TestSuite.run(TestSuite.java:250) at
junit.framework.TestSuite.runTest(TestSuite.java:255) at junit.frame
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9013) Node stop hangs if there was cache activities in Service Processor
Eduard Shangareev created IGNITE-9013:
-
Summary: Node stop hangs if there was cache activities in Service
Processor
Key: IGNITE-9013
URL: https://issues.apache.org/jira/browse/IGNITE-9013
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
I have found this issue while running
IgniteServiceReassignmentTest#testZombieAssignmentsCleanup.
And test hanged with:
{code}
"main@1" prio=5 tid=0x1 nid=NA waiting
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Unsafe.java:-1)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at
java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1465)
at
java.util.concurrent.Executors$DelegatedExecutorService.awaitTermination(Executors.java:675)
at
org.apache.ignite.internal.util.IgniteUtils.shutdownNow(IgniteUtils.java:4749)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStop(GridServiceProcessor.java:327)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2130)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2077)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2595)
- locked <0x273d> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2558)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1088)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1131)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1109)
at
org.apache.ignite.internal.processors.service.IgniteServiceReassignmentTest.afterTest(IgniteServiceReassignmentTest.java:82)
at
org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1694)
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:497)
at junit.framework.TestCase.runBare(TestCase.java:146)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
{code}
{code}
"srvc-deploy-#811%service.IgniteServiceReassignmentTest2%@5000" prio=5
tid=0x3d9 nid=NA waiting
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Unsafe.java:-1)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$37.op(GridCacheAdapter.java:2959)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4150)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAndRemove0(GridCacheAdapter.java:2948)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAndRemove(GridCacheAdapter.java:2932)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1897)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:2076)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9012) Test IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails
Eduard Shangareev created IGNITE-9012:
-
Summary: Test
IgniteServiceReassignmentTest.testZombieAssignmentsCleanup fails
Key: IGNITE-9012
URL: https://issues.apache.org/jira/browse/IGNITE-9012
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Example:
https://ci.ignite.apache.org/viewLog.html?buildId=1499947=buildResultsDiv=IgniteTests24Java8_Basic1#testNameId4751597304481704825
{test}
[2018-07-16 10:50:03,888][ERROR][main][root] Test failed.
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertFalse(Assert.java:39)
at junit.framework.Assert.assertFalse(Assert.java:47)
at junit.framework.TestCase.assertFalse(TestCase.java:219)
at
org.apache.ignite.internal.processors.service.IgniteServiceReassignmentTest.testZombieAssignmentsCleanup(IgniteServiceReassignmentTest.java:237)
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:2087)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2002)
at java.lang.Thread.run(Thread.java:748)
{test}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8955) Checkpoint can't get write lock if massive eviction on node start started
Eduard Shangareev created IGNITE-8955: - Summary: Checkpoint can't get write lock if massive eviction on node start started Key: IGNITE-8955 URL: https://issues.apache.org/jira/browse/IGNITE-8955 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Many sys-threads start eviction and start being throttled, so they couldn't proceed because of it, while checkpoint couldn't start because they hold checkpoint read lock. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8911) While cache is restarting it's possible to start new cache with this name
Eduard Shangareev created IGNITE-8911: - Summary: While cache is restarting it's possible to start new cache with this name Key: IGNITE-8911 URL: https://issues.apache.org/jira/browse/IGNITE-8911 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev We have the state "restarting" for caches when we certainly now that these caches would start at some moment in future. But we could start new cache with the same name. Plus, NPE is throwing when we try to get proxy for such caches (in "restarting" state). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8849) Split suites to achieve 1 hour per suite run
Eduard Shangareev created IGNITE-8849: - Summary: Split suites to achieve 1 hour per suite run Key: IGNITE-8849 URL: https://issues.apache.org/jira/browse/IGNITE-8849 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8814) Deadlock on node stop in tests
Eduard Shangareev created IGNITE-8814:
-
Summary: Deadlock on node stop in tests
Key: IGNITE-8814
URL: https://issues.apache.org/jira/browse/IGNITE-8814
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
The issue is in synchronization in IgnitionEx$IgniteNamedInstance.stop0.
I think, we should add guard and don't try to stop node again if stopping is in
progress.
{code}
"tcp-client-disco-msg-worker-#467%client%" #8733 prio=5 os_prio=0
tid=0x7fbdbe55f800 nid=0x5cd3 waiting for monitor entry [0x7fbc331ef000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2559)
- waiting to lock <0x00078c4e7430> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2551)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:372)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3404)
at
org.apache.ignite.internal.IgniteKernal.onReconnected(IgniteKernal.java:3891)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:830)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:589)
- locked <0x00078c6b81b0> (a java.lang.Object)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2423)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2402)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:2047)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1896)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1788)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}
{code}
"main" #1 prio=5 os_prio=0 tid=0x7fbdbc00e800 nid=0x3a56 in Object.wait()
[0x7fbdc2f19000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1252)
- locked <0x00078c4e7290> (a
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker)
at java.lang.Thread.join(Thread.java:1326)
at
org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4608)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStop(ClientImpl.java:313)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2079)
at
org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1675)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2191)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2069)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2588)
- locked <0x00078c4e7430> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2551)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:372)
at org.apache.ignite.Ignition.stop(Ignition.java:229)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1087)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1127)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1108)
at
org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotNotStableTopologiesTest.afterTest(IgniteDbSnapshotNotStableTopologiesTest.java:251)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8673) Reconcile isClient* methods
Eduard Shangareev created IGNITE-8673: - Summary: Reconcile isClient* methods Key: IGNITE-8673 URL: https://issues.apache.org/jira/browse/IGNITE-8673 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Now isClient (Mode, Cache and so on) method semantic could mean different things: -the same as IgniteConfiguration#setClientMode; -or the way how a node is connected to cluster (in the ring or not). Almost in all cases, we need the first thing, but actually methods could return second. For example, ClusterNode.isClient means second, but all of us use as first. So, I propose to make all methods return first. And if there are places which require second replace them with the usage of forceClientMode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8672) Get rid of TcpDiscoverySpi#setForceServerMode
Eduard Shangareev created IGNITE-8672: - Summary: Get rid of TcpDiscoverySpi#setForceServerMode Key: IGNITE-8672 URL: https://issues.apache.org/jira/browse/IGNITE-8672 Project: Ignite Issue Type: Task Reporter: Eduard Shangareev Fix For: 3.0 It should have been already deleted at 2.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8578) .Net Add support baseline auto-adjust parameters (definition, run-time change)
Eduard Shangareev created IGNITE-8578: - Summary: .Net Add support baseline auto-adjust parameters (definition, run-time change) Key: IGNITE-8578 URL: https://issues.apache.org/jira/browse/IGNITE-8578 Project: Ignite Issue Type: New Feature Reporter: Eduard Shangareev Fix For: 2.6 We would introduce at IGNITE-8571 new parameters. We need their support in .Net side. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8576) Change Baseline auto-adjust parameters via SQL
Eduard Shangareev created IGNITE-8576: - Summary: Change Baseline auto-adjust parameters via SQL Key: IGNITE-8576 URL: https://issues.apache.org/jira/browse/IGNITE-8576 Project: Ignite Issue Type: New Feature Reporter: Eduard Shangareev Fix For: 2.6 We would introduce at IGNITE-8571 new parameters. We need to have option change them via SQL. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8575) Change Baseline auto-adjust parameters via console.sh
Eduard Shangareev created IGNITE-8575: - Summary: Change Baseline auto-adjust parameters via console.sh Key: IGNITE-8575 URL: https://issues.apache.org/jira/browse/IGNITE-8575 Project: Ignite Issue Type: New Feature Reporter: Eduard Shangareev Fix For: 2.6 We would introduce at IGNITE-8571 new parameters. We need to have option change them via JMX. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8574) Change Baseline auto-adjust parameters via JMX
Eduard Shangareev created IGNITE-8574: - Summary: Change Baseline auto-adjust parameters via JMX Key: IGNITE-8574 URL: https://issues.apache.org/jira/browse/IGNITE-8574 Project: Ignite Issue Type: New Feature Reporter: Eduard Shangareev Fix For: 2.6 We would introduce at IGNITE-8571 new parameters. We need to have option change them via JMX. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8573) Save baseline auto-adjust parameters to metastore
Eduard Shangareev created IGNITE-8573: - Summary: Save baseline auto-adjust parameters to metastore Key: IGNITE-8573 URL: https://issues.apache.org/jira/browse/IGNITE-8573 Project: Ignite Issue Type: New Feature Reporter: Eduard Shangareev Fix For: 2.6 We would introduce at IGNITE-8048 new parameters. They should be saved in the metastore and restored from it on node/cluster restart. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8571) Baseline auto-adjust feature
Eduard Shangareev created IGNITE-8571: - Summary: Baseline auto-adjust feature Key: IGNITE-8571 URL: https://issues.apache.org/jira/browse/IGNITE-8571 Project: Ignite Issue Type: New Feature Reporter: Eduard Shangareev Now we have only one way to change BLAT - manually update it via console.sh or API. We need to add the possibility to change it automatically. Adjust to current topology. So, I propose 3 new parameters which would be responsible to tune this feature. 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto adjusting baseline. 2. autoAdjustTimeout - time which we would wait after the actual topology change. But it would be reset if new discovery event happened. (node join/exit). 3. autoAdjustMaxTimeout - time which we would wait from the first dicovery event in the chain. If we achieved it than we would change BLAT right away (no matter were another node join/exit happened or not). We need to change API next way: 1. org.apache.ignite.IgniteCluster *Add* isBaselineAutoAdjustEnabled() setBaselineAutoAdjustEnabled(boolean enabled); setBaselineAutoAdjustTimeout(long timeoutInMs); setBaselineAutoAdjustMaxTimeout(long timeoutInMs); 2. org.apache.ignite.configuration.IgniteConfiguration *Add* IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled); IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs); IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs); Also, we need to ensure that all nodes would have the same parameters. And we should be able to survive coordinator left during parameters changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8414) In-memory cache should use BLAT as their Affinity Topology
Eduard Shangareev created IGNITE-8414: - Summary: In-memory cache should use BLAT as their Affinity Topology Key: IGNITE-8414 URL: https://issues.apache.org/jira/browse/IGNITE-8414 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Assignee: Eduard Shangareev Now in-memory caches use all active server nodes as affinity topology and it changes with each node join and exit. What differs from persistent caches behavior which uses BLAT (BaseLine Affinity Topology) as their affinity topology. It causes problems: - we lose (in general) co-location between different caches; - we can't avoid PME when a non-BLAT node joins cluster; - implementation should consider 2 different approaches to affinity calculation. To handle these problems we should make in-memory and persistent cache work similar. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8388) Improve SQL functionality test coverage
Eduard Shangareev created IGNITE-8388: - Summary: Improve SQL functionality test coverage Key: IGNITE-8388 URL: https://issues.apache.org/jira/browse/IGNITE-8388 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev IGNITE-7628 shows test coverage lack. We should add tests with basic SQL scenarios and BLT: 1. With node in a cluster which is not in BLT. 2. With offline node in BLT. 3. 1 + 2. I believe, that we should start with extending next test: org.apache.ignite.internal.processors.cache.IgniteCacheAbstractFieldsQuerySelfTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8380) Affinity node calculation doesn't take into account BLT
Eduard Shangareev created IGNITE-8380: - Summary: Affinity node calculation doesn't take into account BLT Key: IGNITE-8380 URL: https://issues.apache.org/jira/browse/IGNITE-8380 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8185) There is deadlock when client tries to reconnect and node stop was initiated simultaneously
Eduard Shangareev created IGNITE-8185:
-
Summary: There is deadlock when client tries to reconnect and node
stop was initiated simultaneously
Key: IGNITE-8185
URL: https://issues.apache.org/jira/browse/IGNITE-8185
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Stack traces of these 2 activities which deadlock:
{code}
"tcp-client-disco-msg-worker-#493%client%" #7712 prio=5 os_prio=0
tid=0x7f5e06731000 nid=0x520f waiting for monitor entry [0x7f5c7adeb000]
java.lang.Thread.State: BLOCKED (on object monitor)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2519)
- waiting to lock <0x0007a5fe6138> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2511)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:368)
at org.apache.ignite.Ignition.stop(Ignition.java:224)
at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3439)
at
org.apache.ignite.internal.IgniteKernal.onReconnected(IgniteKernal.java:3926)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:812)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:578)
- locked <0x0007a5fe6358> (a java.lang.Object)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2425)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2404)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processNodeAddFinishedMessage(ClientImpl.java:2049)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1898)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1792)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}
{code}
"main" #1 prio=5 os_prio=0 tid=0x7f5e0400e800 nid=0x340c in Object.wait()
[0x7f5e09fbb000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1252)
- locked <0x0007a5fe5f98> (a
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker)
at java.lang.Thread.join(Thread.java:1326)
at
org.apache.ignite.internal.util.IgniteUtils.join(IgniteUtils.java:4603)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStop(ClientImpl.java:313)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStop(TcpDiscoverySpi.java:2061)
at
org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1612)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2238)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2116)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2548)
- locked <0x0007a5fe6138> (a
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2511)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:368)
at org.apache.ignite.Ignition.stop(Ignition.java:224)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1027)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1067)
at
org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1048)
at
org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotNotStableTopologiesTest.afterTest(IgniteDbSnapshotNotStableTopologiesTest.java:241)
at
org.gridgain.grid.internal.processors.cache.database.IgniteDbSnapshotNotStableTopologiesMultiNodeTest.afterTest(IgniteDbSnapshotNotStableTopologiesMultiNodeTest.java:83)
at
org.apache.ignite.testframework.junits.GridAbstractTest.tearDown(GridAbstractTest.java:1624)
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.tearDown(GridCommonAbstractTest.java:492)
at junit.framework.TestCase.runBare(TestCase.java:146)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at
[jira] [Created] (IGNITE-8116) Historic WAL rebalance fails
Eduard Shangareev created IGNITE-8116:
-
Summary: Historic WAL rebalance fails
Key: IGNITE-8116
URL: https://issues.apache.org/jira/browse/IGNITE-8116
Project: Ignite
Issue Type: Bug
Components: persistence
Reporter: Eduard Shangareev
Fix For: 2.5
So, my reproducer fails because rebalance is never completed.
Rebalance fails with next error:
{code}
Exception in thread "sys-#95%wal.IgniteWalRebalanceTest0%"
java.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:390)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:364)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:372)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:357)
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.access$700(GridCacheIoManager.java:99)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1603)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2752)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1516)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1485)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
Reproducer:
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.persistence.db.wal;
import java.util.concurrent.TimeUnit;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.CacheRebalanceMode;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cache.query.annotations.QuerySqlField;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.configuration.WALMode;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.util.typedef.internal.S;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import static
org.apache.ignite.IgniteSystemProperties.IGNITE_PDS_WAL_REBALANCE_THRESHOLD;
/**
* Historic WAL rebalance test
*/
public class IgniteWalRebalanceTest extends GridCommonAbstractTest {
/** Cache name. */
private static final String CACHE_NAME = "cache";
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String gridName)
throws Exception {
System.setProperty(IGNITE_PDS_WAL_REBALANCE_THRESHOLD, "0"); //to make
all rebalance wal-based
IgniteConfiguration cfg = super.getConfiguration(gridName);
CacheConfiguration ccfg = new
[jira] [Created] (IGNITE-8114) Add fail recovery mechanism to tracking pages
Eduard Shangareev created IGNITE-8114: - Summary: Add fail recovery mechanism to tracking pages Key: IGNITE-8114 URL: https://issues.apache.org/jira/browse/IGNITE-8114 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.5 Now we just assert that last saved tag in tracking page should be not greater than passed one. But because of different issues, it could happen. So, I suggest to handle it by adding new "corruption" state to tracking state. If tracking page is in a corrupted state than we would throw an exception on any querying of the tracking page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8007) We should treat as empty any partition as empty if it doesn't have any data
Eduard Shangareev created IGNITE-8007: - Summary: We should treat as empty any partition as empty if it doesn't have any data Key: IGNITE-8007 URL: https://issues.apache.org/jira/browse/IGNITE-8007 Project: Ignite Issue Type: Bug Components: persistence Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.5 GridCacheOffheapManager#addPartition Now we take into account was lastIndex = 0 or not, but it doesn't matter. Partition doesn't have any data, so it's empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7947) Not all OWNING partitions saved in PartitionAllocationMap during checkpoint
Eduard Shangareev created IGNITE-7947: - Summary: Not all OWNING partitions saved in PartitionAllocationMap during checkpoint Key: IGNITE-7947 URL: https://issues.apache.org/jira/browse/IGNITE-7947 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.5 In checkpoint begin listeners we collect PartitionAllocationMap in offheap managers. But if rowStore is null than we ignore this partition in any case even if we own it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7676) Add affinity version to snapshot plugin stub
Eduard Shangareev created IGNITE-7676: - Summary: Add affinity version to snapshot plugin stub Key: IGNITE-7676 URL: https://issues.apache.org/jira/browse/IGNITE-7676 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Assignee: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7653) Issue with saved license causes snapshot test fails
Eduard Shangareev created IGNITE-7653:
-
Summary: Issue with saved license causes snapshot test fails
Key: IGNITE-7653
URL: https://issues.apache.org/jira/browse/IGNITE-7653
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Peter Ivanov
Example of fails
https://ggtc.gridgain.com/viewLog.html?buildId=1082616=buildResultsDiv=id8xIgniteGridGainTestsJava8_DbXSnapshotsSecurity#testNameId-6967724399324938567
{code}
org.apache.ignite.IgniteCheckedException: Snapshot feature is not allowed by
the licence.
{code}
It happens time to time. We rely on default license in tests where Ultimate
features are enabled.
But on some agents license file is presented which would be read by nodes and
because of it ultimate features would be disabled.
Another observation is that it happens only with windows-agents.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7651) Assertion error on cache start
Eduard Shangareev created IGNITE-7651:
-
Summary: Assertion error on cache start
Key: IGNITE-7651
URL: https://issues.apache.org/jira/browse/IGNITE-7651
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192,
headerSize=4096
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7626) Unify code in test which clean up persistence directories
Eduard Shangareev created IGNITE-7626: - Summary: Unify code in test which clean up persistence directories Key: IGNITE-7626 URL: https://issues.apache.org/jira/browse/IGNITE-7626 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7571) [Test fail]
Eduard Shangareev created IGNITE-7571:
-
Summary: [Test fail]
Key: IGNITE-7571
URL: https://issues.apache.org/jira/browse/IGNITE-7571
Project: Ignite
Issue Type: Improvement
Reporter: Eduard Shangareev
{code:java}
[2018-01-30 19:53:21,836][ERROR][main][root] Test failed.
class org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout
was reached before computation completed.
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:242)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:151)
at
org.apache.ignite.internal.processors.cache.IgniteCacheGroupsTest.testNoKeyIntersectTxLocks(IgniteCacheGroupsTest.java:1788)
at
org.apache.ignite.internal.processors.cache.IgniteCacheGroupsTest.testNoKeyIntersect(IgniteCacheGroupsTest.java:1726)
at
org.apache.ignite.internal.processors.cache.IgniteCacheGroupsTest.testNoKeyIntersect(IgniteCacheGroupsTest.java:1536)
at
org.apache.ignite.internal.processors.cache.IgniteCacheGroupsTest.testNoKeyIntersectTx(IgniteCacheGroupsTest.java:1511)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
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:2000)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7521) Add new assertions to FilePageStore and provide page content if read page is broken
Eduard Shangareev created IGNITE-7521: - Summary: Add new assertions to FilePageStore and provide page content if read page is broken Key: IGNITE-7521 URL: https://issues.apache.org/jira/browse/IGNITE-7521 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.4 There is lack of information to troubleshoot a problem with reading corrupted data. Add some information FilePageStore - assertions, page content. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7520) Provide util-methods to get baseline from context
Eduard Shangareev created IGNITE-7520: - Summary: Provide util-methods to get baseline from context Key: IGNITE-7520 URL: https://issues.apache.org/jira/browse/IGNITE-7520 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7389) DataStreamer hangs if exception was thrown during addData which isn't IgniteException
Eduard Shangareev created IGNITE-7389:
-
Summary: DataStreamer hangs if exception was thrown during addData
which isn't IgniteException
Key: IGNITE-7389
URL: https://issues.apache.org/jira/browse/IGNITE-7389
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
I have written test which starts cache on one node and right after it starts
dataStreamer on another node. Which hangs on close method because {{resFut}}
will never be done.
{code}
java.lang.IllegalStateException: Getting affinity for topology version earlier
than affinity is calculated [locNode=TcpDiscoveryNode
[id=ad14d7f6-5895-4038-ba5e-cc487ab0, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2,
lastExchangeTime=1515672065430, loc=true, ver=2.4.0#19700101-sha1:,
isClient=false], grp=PART-G2, topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=3], head=AffinityTopologyVersion [topVer=4, minorTopVer=4],
history=[AffinityTopologyVersion [topVer=4, minorTopVer=4]]]
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:603)
at
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.assignment(GridCacheAffinityManager.java:243)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.affinityCache(GridAffinityProcessor.java:375)
at
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:187)
at
org.apache.ignite.internal.processors.cacheobject.IgniteCacheObjectProcessorImpl.partition(IgniteCacheObjectProcessorImpl.java:267)
at
org.apache.ignite.internal.processors.cacheobject.IgniteCacheObjectProcessorImpl.toCacheKeyObject0(IgniteCacheObjectProcessorImpl.java:135)
at
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheKeyObject(CacheObjectBinaryProcessorImpl.java:805)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:581)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:555)
at
org.gridgain.grid.internal.processors.cache.database.AbstractSnapshotTest$2.run(AbstractSnapshotTest.java:404)
at
org.apache.ignite.testframework.GridTestUtils$6.run(GridTestUtils.java:933)
at
org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1278)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{code}
The best solution is waiting for topology on which cache should be started.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6720) Move operation with file system outside checkpoint write lock
Eduard Shangareev created IGNITE-6720: - Summary: Move operation with file system outside checkpoint write lock Key: IGNITE-6720 URL: https://issues.apache.org/jira/browse/IGNITE-6720 Project: Ignite Issue Type: Improvement Security Level: Public (Viewable by anyone) Reporter: Eduard Shangareev Assignee: Eduard Shangareev There could be long-running operation in onMarkCheckPointBegin call. So, to move them outside write lock holding block make possible make some operations possible to async (for example, making onMarkCheckPointBegin return Future). During this block is in progress no caches updated are allowed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6577) During start cache we should check temporary file existence besides lock file
Eduard Shangareev created IGNITE-6577: - Summary: During start cache we should check temporary file existence besides lock file Key: IGNITE-6577 URL: https://issues.apache.org/jira/browse/IGNITE-6577 Project: Ignite Issue Type: Bug Affects Versions: 2.2 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.4 Now we discard content of cache directory if there is lock file because it means that cache was not completely restored. But except it, there could be temporary directory and if there is marker file it means that cache restore wasn't completed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6512) Need a possibility to start caches without discarding their 'restarting' state
Eduard Shangareev created IGNITE-6512: - Summary: Need a possibility to start caches without discarding their 'restarting' state Key: IGNITE-6512 URL: https://issues.apache.org/jira/browse/IGNITE-6512 Project: Ignite Issue Type: Improvement Reporter: Eduard Shangareev Now we always discard restarting state on cache while it is starting. But sometimes we need extra steps before making caches available from public API. So, I suggest adding a new method which would be called when we want to make caches available for public API clients. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6460) Wrong consistentId for lightweight ClusterNode instances
Eduard Shangareev created IGNITE-6460: - Summary: Wrong consistentId for lightweight ClusterNode instances Key: IGNITE-6460 URL: https://issues.apache.org/jira/browse/IGNITE-6460 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 2.3 I have introduced new constructor for TcpDiscoveryNode to create lightweight instances to store them on disc or etc. But to save consistentId we need not only keep it in field, but also add to node attributes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6434) Assertion error in checkpointer during topology change
Eduard Shangareev created IGNITE-6434:
-
Summary: Assertion error in checkpointer during topology change
Key: IGNITE-6434
URL: https://issues.apache.org/jira/browse/IGNITE-6434
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
Priority: Critical
{code}
2017-09-11 21:35:22.195
[ERROR][db-checkpoint-thread-#101%node1%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
Runtime error caught during grid runnable execution: GridWorker
[name=db-checkpoint-thread, igniteInstanceName=cache1, finished=false,
hashCode=1326137503, interrupted=false, runner=db-checkpoint-thread-#101%node1%]
java.lang.IllegalStateException: Failed to add new partition to the partitions
state (no enough space reserved) [partId=459, reserved=459]
at
org.apache.ignite.internal.pagemem.wal.record.CacheState.addPartitionState(CacheState.java:50)
~[ignite-core-2.1.4.jar:2.1.4]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2189)
~[ignite-core-2.1.4.jar:2.1.4]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1954)
~[ignite-core-2.1.4.jar:2.1.4]
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1879)
~[ignite-core-2.1.4.jar:2.1.4]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
~[ignite-core-2.1.4.jar:2.1.4]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_121]
{code}
After checkpoint thread died.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6433) We need to cancel eviction instead of waiting it when we should own a partition because we had lost it
Eduard Shangareev created IGNITE-6433: - Summary: We need to cancel eviction instead of waiting it when we should own a partition because we had lost it Key: IGNITE-6433 URL: https://issues.apache.org/jira/browse/IGNITE-6433 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.3 If PartitionLossPolicy.IGNORE is used and we have lost some partition which would belong to us because of affinity assignment and its state was RENTING then we would wait for its eviction completing what would hang cluster (the time of exchange would significantly increase). Instead of waiting we should cancel eviction and it's all. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6425) Races during transaction finalization
Eduard Shangareev created IGNITE-6425: - Summary: Races during transaction finalization Key: IGNITE-6425 URL: https://issues.apache.org/jira/browse/IGNITE-6425 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6423) LFD could be corrupted if partition have been evicted and returned to node
Eduard Shangareev created IGNITE-6423: - Summary: LFD could be corrupted if partition have been evicted and returned to node Key: IGNITE-6423 URL: https://issues.apache.org/jira/browse/IGNITE-6423 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Priority: Critical So, what is going on? Partition had been changed, its pages had been put to checkpoint pages. After it partition was evicted, checkpoint started. We are allocating a page and because it's already in checkpoint we copy the empty page to copy it on disk. If we restart right now we will read the empty page from disk. Therefore assertion error would be thrown etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6342) Exchange is hanging on eviction
Eduard Shangareev created IGNITE-6342: - Summary: Exchange is hanging on eviction Key: IGNITE-6342 URL: https://issues.apache.org/jira/browse/IGNITE-6342 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev I wrote test which stop/start random node, the test hangs time to time on exchange. As I see, exchange-thread waiting for partition eviction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6277) Convert WAL to human readable form
Eduard Shangareev created IGNITE-6277:
-
Summary: Convert WAL to human readable form
Key: IGNITE-6277
URL: https://issues.apache.org/jira/browse/IGNITE-6277
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
Fix For: 2.3
Now there is no way to make wal visible or understandable without coding.
I propose to write utility which would convert any given compatible WAL to
textual form.
Something like this:
{code}
[W] InsertRecord [idx=19, io=H2ExtrasLeafIO[ver=1], rightId=,
super=PageDeltaRecord [grpId=2141373875, pageId=00020011,
super=WALRecord [size=61, chainSize=0, pos=FileWALPointer [idx=0,
fileOffset=2504497, len=61, forceFlush=false], type=BTREE_PAGE_INSERT]]]
[W] DataRecord [writeEntries=[DataEntry [op=CREATE, writeVer=GridCacheVersion
[topVer=116006687, order=0, nodeOrder=1], partId=29, partCnt=33]],
super=WALRecord [size=171, chainSize=0, pos=FileWALPointer [idx=0,
fileOffset=2504558, len=171, forceFlush=false], type=DATA_RECORD]]
[W] PagesListRemovePageRecord [rmvdPageId=0001000c002f,
pageId=0001000c000a, grpId=-1368047377, super=PageDeltaRecord
[grpId=-1368047377, pageId=0001000c000a, super=WALRecord [size=37,
chainSize=0, pos=FileWALPointer [idx=0, fileOffset=2504729, len=37,
forceFlush=false], type=PAGES_LIST_REMOVE_PAGE]]]
[W] DataPageInsertRecord [super=PageDeltaRecord [grpId=-1368047377,
pageId=0001000c002f, super=WALRecord [size=76, chainSize=0,
pos=FileWALPointer [idx=0, fileOffset=2504766, len=76, forceFlush=false],
type=DATA_PAGE_INSERT_RECORD]]]
[W] PagesListAddPageRecord [dataPageId=0001000c002f, super=PageDeltaRecord
[grpId=-1368047377, pageId=0001000c000b, super=WALRecord [size=37,
chainSize=0, pos=FileWALPointer [idx=0, fileOffset=2504842, len=37,
forceFlush=false], type=PAGES_LIST_ADD_PAGE]]]
[W] DataPageSetFreeListPageRecord [freeListPage=281526516318219,
super=PageDeltaRecord [grpId=-1368047377, pageId=0001000c002f,
super=WALRecord [size=37, chainSize=0, pos=FileWALPointer [idx=0,
fileOffset=2504879, len=37, forceFlush=false],
type=DATA_PAGE_SET_FREE_LIST_PAGE]]]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6175) JVM Crash in "Ignite Binary Objects Simple Mapper Basic" suite
Eduard Shangareev created IGNITE-6175:
-
Summary: JVM Crash in "Ignite Binary Objects Simple Mapper Basic"
suite
Key: IGNITE-6175
URL: https://issues.apache.org/jira/browse/IGNITE-6175
Project: Ignite
Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Eduard Shangareev
Fix For: 2.2
JVM crash dump and logs you could find here
https://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteBinarySImpleMapperBasic=785893_Ignite20Tests_IgniteBinarySImpleMapperBasic=pull/2380/head
{code}
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f6a0274a13f, pid=3507, tid=140092082124544
#
# JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# J 10572 C2
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readLock(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;)J
(39 bytes) @ 0x7f6a0274a13f [0x7f6a02749ba0+0x59f]
#
# Core dump written. Default location:
/data/teamcity/work/820be461cd64b574/core or core.3507
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6068) We try to add entry to partition which was concurrently evicted
Eduard Shangareev created IGNITE-6068:
-
Summary: We try to add entry to partition which was concurrently
evicted
Key: IGNITE-6068
URL: https://issues.apache.org/jira/browse/IGNITE-6068
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
Fix For: 2.2
https://ci.ignite.apache.org/viewLog.html?buildId=768819=buildResultsDiv=Ignite20Tests_IgniteQueries2
{code}
rg.apache.ignite.internal.processors.query.schema.SchemaOperationException:
Schema change operation failed: Adding entry to partition that is concurrently
evicted [part=817, shouldBeMoving=false, belongs=false,
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=0],
curTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=0]]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.processIndexOperationLocal(GridQueryProcessor.java:1290)
at
org.apache.ignite.internal.processors.query.schema.SchemaOperationWorker.body(SchemaOperationWorker.java:108)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by:
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtInvalidPartitionException:
Adding entry to partition that is concurrently evicted [part=817,
shouldBeMoving=false, belongs=false, topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=0], curTopVer=AffinityTopologyVersion [topVer=4, minorTopVer=0]]
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:752)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:644)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:69)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:88)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:933)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:524)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:924)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processKey(SchemaIndexCacheVisitorImpl.java:141)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.processPartition(SchemaIndexCacheVisitorImpl.java:120)
at
org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl.visit(SchemaIndexCacheVisitorImpl.java:90)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.dynamicIndexCreate(IgniteH2Indexing.java:684)
at
org.apache.ignite.internal.processors.cache.index.DynamicIndexAbstractConcurrentSelfTest$BlockingIndexing.dynamicIndexCreate(DynamicIndexAbstractConcurrentSelfTest.java:1065)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.processIndexOperationLocal(GridQueryProcessor.java:1276)
at
org.apache.ignite.internal.processors.query.schema.SchemaOperationWorker.body(SchemaOperationWorker.java:108)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6005) [Test failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
Eduard Shangareev created IGNITE-6005:
-
Summary: [Test failed]
GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
Key: IGNITE-6005
URL: https://issues.apache.org/jira/browse/IGNITE-6005
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
Fix For: 2.2
Example of fail
https://ci.ignite.apache.org/viewLog.html?buildId=762788=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures
Typical problem is
{code}
org.apache.ignite.IgniteInterruptedException: Failed to wait for asynchronous
operation permit (thread got interrupted).
at org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:805)
at org.apache.ignite.internal.util.IgniteUtils$3.apply(IgniteUtils.java:803)
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:961)
at
org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1026)
at
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.InterruptedException: null
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301)
at java.util.concurrent.Semaphore.acquire(Semaphore.java:317)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOpAcquire(GridCacheAdapter.java:4314)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4177)
at
org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:196)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get0(GridCacheAdapter.java:4509)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4490)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1324)
at
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:329)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$5.applyx(DataStructuresProcessor.java:635)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1519)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeDataStructure(DataStructuresProcessor.java:629)
at
org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.removeSemaphore(DataStructuresProcessor.java:1188)
at
org.apache.ignite.internal.processors.datastructures.GridCacheSemaphoreImpl.close(GridCacheSemaphoreImpl.java:1023)
at
org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:458)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6000) Assertion during destroy GridH2Table
Eduard Shangareev created IGNITE-6000:
-
Summary: Assertion during destroy GridH2Table
Key: IGNITE-6000
URL: https://issues.apache.org/jira/browse/IGNITE-6000
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
Fix For: 2.2
It was found here
org.apache.ignite.internal.processors.cache.index.DynamicIndexReplicatedAtomicConcurrentSelfTest#testConcurrentOperationsAndCacheStartStopMultithreaded
{code}
[18:25:16] (err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$1...@6000c93bjava.lang.AssertionError:
{}
at
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.destroy(GridH2Table.java:508)
at
org.apache.ignite.internal.processors.query.h2.H2TableDescriptor.onDrop(H2TableDescriptor.java:346)
at
org.apache.ignite.internal.processors.query.h2.H2Schema.drop(H2Schema.java:114)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.unregisterCache(IgniteH2Indexing.java:2154)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop0(GridQueryProcessor.java:1481)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStop(GridQueryProcessor.java:863)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1225)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStop(GridCacheProcessor.java:1999)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onExchangeDone(GridCacheProcessor.java:2149)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1294)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:1812)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processMessage(GridDhtPartitionsExchangeFuture.java:1479)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:110)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$1.apply(GridDhtPartitionsExchangeFuture.java:1422)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$1.apply(GridDhtPartitionsExchangeFuture.java:1410)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:382)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:352)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1410)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1425)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:127)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:292)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:290)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2294)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:2273)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1042)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:561)
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:99)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
[jira] [Created] (IGNITE-5999) Assertion Moving partition is below zero
Eduard Shangareev created IGNITE-5999:
-
Summary: Assertion Moving partition is below zero
Key: IGNITE-5999
URL: https://issues.apache.org/jira/browse/IGNITE-5999
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
Fix For: 2.2
{code}
java.lang.AssertionError: -10
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.hasMovingPartitions(GridDhtPartitionMap.java:135)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.hasMovingPartitions(GridDhtPartitionTopologyImpl.java:2116)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.hasMovingPartitions(GridReduceQueryExecutor.java:366)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.isPreloadingActive(GridReduceQueryExecutor.java:354)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:577)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1160)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:114)
at
org.apache.ignite.internal.processors.cache.distributed.near.IgniteCacheQueryNodeRestartSelfTest2$1.applyx(IgniteCacheQueryNodeRestartSelfTest2.java:247)
at
org.apache.ignite.internal.util.lang.GridAbsClosureX.apply(GridAbsClosureX.java:35)
at
org.apache.ignite.internal.util.lang.GridAbsClosure.run(GridAbsClosure.java:50)
at
org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1236)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5998) Assertion during partition creation in tests
Eduard Shangareev created IGNITE-5998:
-
Summary: Assertion during partition creation in tests
Key: IGNITE-5998
URL: https://issues.apache.org/jira/browse/IGNITE-5998
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
Priority: Critical
Fix For: 2.2
It was cause of hang of
DynamicIndexReplicatedAtomicConcurrentSelfTest.testQueryConsistencyMultithreaded
{code}
[2017-08-08
19:02:01,877][ERROR][exchange-worker-#4300529%index.DynamicIndexReplicatedAtomicConcurrentSelfTest1%][CacheAffinitySharedManager]
Failed to initialize cache. Will try to rollback cache start routine.
[cacheName=cache]
class org.apache.ignite.IgniteCheckedException: Failed to register MBean for
component:
org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl@4d0397a2
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.registerMbean(GridCacheProcessor.java:3624)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1637)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1863)
at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:742)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:739)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:468)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1954)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.management.InstanceAlreadyExistsException:
org.apache:clsLdr=6d06d69c,igniteInstanceName=index.DynamicIndexReplicatedAtomicConcurrentSelfTest1,group=cache,name=org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at
org.apache.ignite.internal.util.IgniteUtils.registerCacheMBean(IgniteUtils.java:4574)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.registerMbean(GridCacheProcessor.java:3620)
... 8 more
[2017-08-08
19:02:01,878][ERROR][exchange-worker-#4300529%index.DynamicIndexReplicatedAtomicConcurrentSelfTest1%][GridDhtPartitionsExchangeFuture]
Failed to reinitialize local partitions (preloading will be stopped):
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=1], discoEvt=DiscoveryCustomEvent
[customMsg=DynamicCacheChangeBatch
[id=2490c129e51-bbb352cc-e911-41e1-afd6-67e8ed91809c,
reqs=[DynamicCacheChangeRequest [cacheName=cache, hasCfg=true,
nodeId=fdc8ffc4-3da3-470e-a8ac-5f8b4204, clientStartOnly=false, stop=false,
destroy=false]], exchangeActions=ExchangeActions [startCaches=[cache],
stopCaches=null, startGrps=[cache], stopGrps=[], resetParts=null,
stateChangeRequest=null], startCaches=false], affTopVer=AffinityTopologyVersion
[topVer=4, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=fdc8ffc4-3da3-470e-a8ac-5f8b4204, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:0], discPort=0, order=4, intOrder=4,
lastExchangeTime=1502208121825, loc=false, ver=2.2.0#19700101-sha1:,
isClient=true], topVer=4, nodeId8=0e697ca6, msg=null,
type=DISCOVERY_CUSTOM_EVT, tstamp=1502208121873]], nodeId=fdc8ffc4,
evt=DISCOVERY_CUSTOM_EVT]
java.lang.AssertionError
at
org.apache.ignite.internal.processors.cache.CacheGroupContext.singleCacheContext(CacheGroupContext.java:344)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:189)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.createPartition(GridDhtPartitionTopologyImpl.java:663)
at
[jira] [Created] (IGNITE-5997) [Test Failed] DynamicIndexPartitionedAtomicConcurrentSelfTest.testCoordinatorChange
Eduard Shangareev created IGNITE-5997:
-
Summary: [Test Failed]
DynamicIndexPartitionedAtomicConcurrentSelfTest.testCoordinatorChange
Key: IGNITE-5997
URL: https://issues.apache.org/jira/browse/IGNITE-5997
Project: Ignite
Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
Fix For: 2.2
It fails more often locally on linux machine
http://ci.ignite.apache.org/viewLog.html?buildId=752869=buildResultsDiv=Ignite20Tests_IgniteQueries2#testNameId-4226597044755906475
{code}
SchemaOperationException [code=0, msg=Client node is disconnected (operation
result is unknown).]
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onDisconnected(GridQueryProcessor.java:822)
at
org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:3770)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:749)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:559)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2391)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2370)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1686)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5980) [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
Eduard Shangareev created IGNITE-5980: - Summary: [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover Key: IGNITE-5980 URL: https://issues.apache.org/jira/browse/IGNITE-5980 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Example of failing http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId-4067536648656067727 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
Eduard Shangareev created IGNITE-5979: - Summary: [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync Key: IGNITE-5979 URL: https://issues.apache.org/jira/browse/IGNITE-5979 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Example of failing - http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5978) [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1
Eduard Shangareev created IGNITE-5978: - Summary: [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1 Key: IGNITE-5978 URL: https://issues.apache.org/jira/browse/IGNITE-5978 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Fails locally. Example of failing - http://ci.ignite.apache.org/viewLog.html?buildId=759891=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId677264269171099154. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence
Eduard Shangareev created IGNITE-5977: - Summary: [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence Key: IGNITE-5977 URL: https://issues.apache.org/jira/browse/IGNITE-5977 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Fails locally. Example of failing http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5976) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock
Eduard Shangareev created IGNITE-5976: - Summary: [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock Key: IGNITE-5976 URL: https://issues.apache.org/jira/browse/IGNITE-5976 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Fails locally. Example of failing http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5975) [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure
Eduard Shangareev created IGNITE-5975: - Summary: [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure Key: IGNITE-5975 URL: https://issues.apache.org/jira/browse/IGNITE-5975 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Fails locally. Example of failing - http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-2988875689386264427. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5974) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSemaphore
Eduard Shangareev created IGNITE-5974: - Summary: [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSemaphore Key: IGNITE-5974 URL: https://issues.apache.org/jira/browse/IGNITE-5974 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fix For: 2.2 Fails locally. Example of failing - http://ci.ignite.apache.org/viewLog.html?buildId=755824=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-6847798749379612181 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5973) [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
Eduard Shangareev created IGNITE-5973: - Summary: [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe Key: IGNITE-5973 URL: https://issues.apache.org/jira/browse/IGNITE-5973 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Fix For: 2.1 Success right is 93.3%. Fails locally. Example of failing - http://ci.ignite.apache.org/viewLog.html?buildId=757906=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-979977708202725050 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5972) [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast
Eduard Shangareev created IGNITE-5972: - Summary: [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast Key: IGNITE-5972 URL: https://issues.apache.org/jira/browse/IGNITE-5972 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Eduard Shangareev Fails locally. Flaky one. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails
Eduard Shangareev created IGNITE-5954: - Summary: Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails Key: IGNITE-5954 URL: https://issues.apache.org/jira/browse/IGNITE-5954 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Probably, it's broken after IGNITE-5272. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5943) Communication. We could reject client connection while it has received EVT_NODE_JOINED
Eduard Shangareev created IGNITE-5943: - Summary: Communication. We could reject client connection while it has received EVT_NODE_JOINED Key: IGNITE-5943 URL: https://issues.apache.org/jira/browse/IGNITE-5943 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.0 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Priority: Critical Fix For: 2.2 There is a race between server nodes receive acknowledgment about joining client node and client node starts to think that it is absolutely functional. It would cause to rejecting communication (for example. on requesting data from caches) between the client and servers. The issue happens on really big topologies (> 300 nodes) or when many clients join simultaneously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5871) IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed fails
Eduard Shangareev created IGNITE-5871: - Summary: IgniteCacheP2pUnmarshallingRebalanceErrorTest.testResponseMessageOnUnmarshallingFailed fails Key: IGNITE-5871 URL: https://issues.apache.org/jira/browse/IGNITE-5871 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Success rate is 20%. http://ci.ignite.apache.org/project.html?tab=testDetails=Ignite20Tests=-720637123828878=10 Seems that it was broken in build #179, where [~sboikov] had merged cache groupd (ignite-5075) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5870) IgniteTopologyValidatorGridSplitCacheTest#testTopologyValidator fails
Eduard Shangareev created IGNITE-5870: - Summary: IgniteTopologyValidatorGridSplitCacheTest#testTopologyValidator fails Key: IGNITE-5870 URL: https://issues.apache.org/jira/browse/IGNITE-5870 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Success rate is 10%. History is too short to say when it starts failing. http://ci.ignite.apache.org/project.html?tab=testDetails=Ignite20Tests=-318150309218360964=1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5843) Ignite PDS: We don't save cache configuration if we get it on join
Eduard Shangareev created IGNITE-5843: - Summary: Ignite PDS: We don't save cache configuration if we get it on join Key: IGNITE-5843 URL: https://issues.apache.org/jira/browse/IGNITE-5843 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.1 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Priority: Critical Fix For: 2.2 We don't save cache configuration when we get it on join (new node joins cluster with cache which is not presented on config or on disk). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-4332) Usage of cache.getEntry inside GridCacheQueryManager.runQuery causes to remote operations
Eduard Shangareev created IGNITE-4332: - Summary: Usage of cache.getEntry inside GridCacheQueryManager.runQuery causes to remote operations Key: IGNITE-4332 URL: https://issues.apache.org/jira/browse/IGNITE-4332 Project: Ignite Issue Type: Bug Affects Versions: 1.7 Reporter: Eduard Shangareev Assignee: Eduard Shangareev Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3662) Improving Integration with Spring Data
Eduard Shangareev created IGNITE-3662: - Summary: Improving Integration with Spring Data Key: IGNITE-3662 URL: https://issues.apache.org/jira/browse/IGNITE-3662 Project: Ignite Issue Type: Improvement Components: ignite-spring Affects Versions: 1.7 Reporter: Eduard Shangareev Umbrella ticket for further improvements of support of spring data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3621) Make GridCacheTtlManager singleto
Eduard Shangareev created IGNITE-3621:
-
Summary: Make GridCacheTtlManager singleto
Key: IGNITE-3621
URL: https://issues.apache.org/jira/browse/IGNITE-3621
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.6
Reporter: Eduard Shangareev
Now every cache has own TTL manager, which creates CleanupWorker = new extra
thread. This can cause to extra hundreds of threads (redundant context switches
= performance penalty).
Also, under IGNITE-3513 every put can enter critical section to notify worker.
Obviously, it is not good from performance point of view.
So, my proposal is next:
1. Expiration should be done on every cache action (on exit thread which
updates cache should invoke {{expire}}).
2. TtlManager will exist only in one instance.
3. CleanupWorker will be the only backup if there is no cache activity. It will
wake up with some period to check for work (500 ms, for example).
Moreover, now we keep on-heap pending entries even if a cache is kept off-head.
At least, this issue needs discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
