ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From breischl <breis...@gmail.com>
Subject RE: Deadlock during cache loading
Date Thu, 28 Jun 2018 16:59:45 GMT
>our a stream receiver called invoke() and that in turn did another invoke,
which was the actual bug. 
So Ignite's invoke() implementation called itself?


>It was helpful when we did the invoke using a custom thread pool,
I'm not sure I understand the concept here. Is the idea to have an
ExecutorService in of the StreamReceiver, and use that to call invoke()?


It seems odd that it could get hung up on the get() call since presumably
this is being invoked on the primary, and therefore should not need to go
out anywhere. But I notice that it's still trying to map onto the grid
topology, so maybe if the topology changes before the StreamReceiver is
invoked? Total guess, I have only a vague idea of Ignite internals. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Mime
View raw message