Thanks Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Node-hangs-while-accessing-cache-from-Compute-Task-tp10637p10790.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Dmitry,
Thanks for the detailed explanation.
Do you know if this behavior "It's not allowed to use cache API in
CacheEntryProcessor, query listeners, interceptors and so forth, because it
leads to deadlocks" is documented somewhere?
Thanks,
Gaurav
On Thu, Feb 16, 2017 at 12:16 PM,
Hi,
This is a correct behavior. It's not allowed to use cache API in
CacheEntryProcessor, query listeners, interceptors and so forth, because it
leads to deadlocks. In your example it looks like (threads T1, T2):
T1 put entry -> T1 lock entry -> T1 call listener -> T1 execute job -> T1
wait for