[IGNITE-8338] Cache operations hang after cluster deactivation and activation again

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.4
• Component/s: cache
• Assignee: Unassigned
• Reporter: Pavel Kovalenko
• Created: 20/Apr/18 11:03
• Updated: 29/Dec/20 08:57

Description

Problem:
1) Start several nodes
2) Activate cluster
3) Run cache load
4) Deactivate cluster
5) Activate again

After second activation cache operations hang with following stacktrace:

"cache-load-2" #210 prio=5 os_prio=0 tid=0x00007efbb401b800 nid=0x602b waiting on condition [0x00007efb809b3000]
   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.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:3782)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.publicJCache(GridCacheProcessor.java:3753)
	at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.checkProxyIsValid(GatewayProtectedCacheProxy.java:1486)
	at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1508)
	at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:785)
	at org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTestWithPersistence.lambda$testDeactivateDuringEviction$0(IgniteClusterActivateDeactivateTestWithPersistence.java:316)
	at org.apache.ignite.internal.processors.cache.IgniteClusterActivateDeactivateTestWithPersistence$$Lambda$39/832408842.run(Unknown Source)
	at org.apache.ignite.testframework.GridTestUtils$6.call(GridTestUtils.java:1254)
	at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)

It seems, dynamicStartCache future never completes after second activation.