Ross, The optimization you suggested does not work in the case when remote filter is present, but it indeed works for your case. I created a ticket for this optimization: https://issues.apache.org/jira/browse/IGNITE-3607
2016-07-29 17:51 GMT+03:00 ross.anderson <[email protected]>: > 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 > seconds. > > 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? > > Best, > Ross > > > > -- > 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. >
