ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ross.anderson" <ross.ander...@caplin.com>
Subject Re: Deadlock during Client Continuous Query deserialization
Date Fri, 29 Jul 2016 14:51:34 GMT
Glad to be of assistance
I can confirm that setting the queue limit does resolve the initial problem
of updates getting through, but one `put` is taking between 6 and 50

Out of curiosity, shouldn't one of these cache update notifications be sent
across the wire just once - and then multicast to the query listeners
locally within the client process?
Currently it seems to generate a lot of load - perhaps I need to rethink our
use of continuous queries?


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-tp6565p6620.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message