You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Eduard Shangareev (JIRA)" <ji...@apache.org> on 2019/08/14 13:38:00 UTC

[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)