Hi Naresh, I see deadlocks with 1. com.rover.core.dao.model.admin.AdminPreferenceTable (2 locks) 2. com.rover.core.dao.model.product.assembly.AssemblyUpi2BomTable (2 locks) 3. com.rover.core.dao.model.product.assembly.AssemblyBomUpi2PackageTable, 4. com.rover.core.dao.model.product.ProductVersionInfoTable
Could you please provide a reproducible sample for this issue to move further? I don’t have a clear understanding what can cause this issue and I could not reproduce it. BTW, Please check your configuration, I see versions mismatch (2.3 vs 1.9) in Ignite output: >>> Ignite ver. 2.3.0-SNAPSHOT#19691231-sha1:DEV INFO: IGNITE_HOME=C:\development\software\apache-ignite-fabric-1.9.0-bin Please update IGNITE_HOME to a correct path. Thank you, Alexey From: naresh.goty Sent: Monday, November 6, 2017 5:36 AM To: user@ignite.apache.org Subject: RE: Node failed to startup due to deadlock Hi Alexey, We are still seeing the deadlocks for the scenario i have specified earlier. We tried the below two changes, but still seeing the deadlocks. Can you please provide some pointers about the issue based on the logs and threaddumps attached. 1) As Rajeev mentioned, we tried offloading event handling to application threads. 2) Applied the patch fix (https://issues.apache.org/jira/browse/IGNITE-6380#), but still the same issue. Node1.log <http://apache-ignite-users.70518.x6.nabble.com/file/t1286/Node1.log> Node2.log <http://apache-ignite-users.70518.x6.nabble.com/file/t1286/Node2.log> Node1_AfterNode2_Turndown.tdump <http://apache-ignite-users.70518.x6.nabble.com/file/t1286/Node1_AfterNode2_Turndown.tdump> Node1_AfterNode2_StartedAgain.tdump <http://apache-ignite-users.70518.x6.nabble.com/file/t1286/Node1_AfterNode2_StartedAgain.tdump> Node2_AfteStartedAgain.tdump <http://apache-ignite-users.70518.x6.nabble.com/file/t1286/Node2_AfteStartedAgain.tdump> Regards, Naresh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
