Naresh, Rajeev I've looked through the logs. Node2 is stuck because it is waiting for Node1 (id=96eea214-a2e3-4e0a-b8c6-7fdf3f29727c) partition map exchange response. So it looks like the real deadlock is at Node1 (id=96eea214-a2e3-4e0a-b8c6-7fdf3f29727c)
Can you also send node1 logs and thread dumps from it? I will check them and let you know if it is a known/fixed issue. BTW, please ensure that your event listeners at node1 do not update Ignite caches/etc. It could be the similar case as in [http://apache-ignite-users.70518.x6.nabble.com/Threads-waiting-on-cache-reads-tt17802.html] Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
