Hi Alexey, Thank you for pointing out the problem with caches causing deadlocks. I fixed the classpath pointing to 1.9, but the issue still exists.
Actually we could reproduce deadlock with a scenario when two nodes trying to comeup during same time, and the first node holds lock on a cache. (attached sample code when run in the following order: 1) Start App.java and wait till the cache is locked 2) start App2.java, then we see deadlock on App2. We also tried with patch provided in (IGNITE-6380), but it is rejecting jobs which are waiting. ex=class o.a.i.compute.ComputeExecutionRejectedException: Pending topology found - job execution within lock or transaction was canceled., hasRes=true, isCancelled=false, isOccupied=true] class org.apache.ignite.IgniteException: Remote job threw exception. To summarize our node startup process: 1) Each node upon start, it will create or get the caches. 2) Lock the caches 3) if caches not already loaded, then it will clear the caches, and perform dataload 4) notify through ignite messaging about cache load activities 5) release lock on caches. So, if multiple nodes are starting at the same time, all the nodes will try to perform the above activities. During this process we will ensure that, each cache will be loaded only once. Can you please confirm if the above usecase is supported with ignite? Thanks Naresh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
