Here is JIRA issue: https://issues.apache.org/jira/browse/IGNITE-3606
On Fri, Jul 29, 2016 at 5:48 PM, Semyon Boikov <[email protected]> wrote: > Hi, > > I reproduced this issue, thank you for test! After quick debugging It > seems that this is some problem with Ignite backpressure mechanism in > communication SPI, I'll create JIRA issue with more details. > > As a workaround could you try to disable backpressure: > tcpCommunicationSpi.setMessageQueueLimit(0); > > Thanks! > > On Fri, Jul 29, 2016 at 1:15 PM, ross.anderson <[email protected]> > wrote: > >> Hi, has anyone had a chance to take a look at this? >> I'd imagine it's a critical issue if a client can cause a cluster to >> freeze >> indefinitely based solely on a smallish number of queries running? >> If there's anything else I can provide to assist please do let me know, as >> this is a blocker for us using Ignite. >> Thanks, Ross >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Deadlock-during-Client-Continuous-Query-deserialization-tp6565p6616.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
