Rajeev, I see “WARNING: Failed to wait for partition release future” section in your logs. It includes “WARNING: Pending explicit locks:” with 7 cache locks (GridCacheExplicitLockSpan) GridCacheExplicitLockSpan details don’t have specific information about cache operation but they have topology version. (topVer=3).
So, very probably these locks were taken on some event when Node 2 left the cluster 7:50:31 PM INFO: Topology snapshot [ver=2, servers=2, clients=0, CPUs=8, heap=5.5GB] 8:00:15 PM INFO: Topology snapshot [ver=3, servers=1, clients=0, CPUs=8, heap=2.0GB] 8:08:17 PM INFO: Topology snapshot [ver=4, servers=2, clients=0, CPUs=8, heap=5.5GB] Thank you, Alexey From: rajivgandhi Sent: Thursday, November 2, 2017 7:43 PM To: user@ignite.apache.org Subject: Re: Node failed to startup due to deadlock Can you please also help us understand, how you diagnized the symptom? It is hard to understand deadlocks for distributed operations. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
