Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EF705200B50 for ; Fri, 29 Jul 2016 17:03:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EE014160AA6; Fri, 29 Jul 2016 15:03:53 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1A15D160A6E for ; Fri, 29 Jul 2016 17:03:52 +0200 (CEST) Received: (qmail 40601 invoked by uid 500); 29 Jul 2016 15:03:52 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 40581 invoked by uid 99); 29 Jul 2016 15:03:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2016 15:03:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C438C1A5C94 for ; Fri, 29 Jul 2016 15:03:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.279 X-Spam-Level: * X-Spam-Status: No, score=1.279 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id VdVkr-TQm9aU for ; Fri, 29 Jul 2016 15:03:49 +0000 (UTC) Received: from mail-qt0-f170.google.com (mail-qt0-f170.google.com [209.85.216.170]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 9F0895FCF3 for ; Fri, 29 Jul 2016 15:03:49 +0000 (UTC) Received: by mail-qt0-f170.google.com with SMTP id u25so67881857qtb.1 for ; Fri, 29 Jul 2016 08:03:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=+OEOcpE9Ef5EHOesEOqSCoRIEfxcWv5QsaqK/vfCy2M=; b=saFAut+yUAypGyNYtUzw5ra/0lN0M33o8b99ye8QYjhWH/QUP516qcxuIfTOjn8AG8 N1UG8KpUQNcInrBOUXPUjfpPxTeXdTKJ67YwLW5f9Qmf+GiYhR6cmV0Irm9dG9z8MJlS CW4uo7nM3tt4kVYtO7A8jFWwrHFhcr4rXXtfc9BfRogJG1ed8noTg2/NEDHcxHevUFQU Y/E1lKbQjQFfdyMjIc3OtFDamN9wch9pL5gv/CMSzFKXNtg0rxc/9AHbVj4kHMh09ql3 D2MlVoHQRaANmiqgXO7DIWSSy1I+2G70IdaDgkab9P8294vHzPPKzS+psFUd7Kp+yZdC 6pAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=+OEOcpE9Ef5EHOesEOqSCoRIEfxcWv5QsaqK/vfCy2M=; b=Gu2lVna++ep4a3VaC8tax4InZKe0hzX6lPFGchasI3A4bAmO7dFQuwBFhjOE5IOS+E +76NdFL8S7ZK8qD2bcKZAL6foSjfS8V1F0aDxMh7qzoYD55+nDPwIyUCHIyhPmklfp/4 tgzTExUOXWQ8AOP4IYhpRMb+9UAIByXegSuogto+6lY9JIqdB0jk9Z5iXRc+mjjrZV1u lA2/19tfXq/dY8dudCHKBVd0FNBjCx3Q59LjBdYcUKrQZ8A8/ff6m/sisN2xAj1uKUUm yumPaFFkEteBV1bpP6IAXFT5QnVjJm6BTuYmThZ5W9nPtLYzEZ/2J8h27IAYXHnWkxwx bbtg== X-Gm-Message-State: AEkoousnAD/1v+lZkkEYBxArZK6lpaWcTihDqEi70u58oLRqGco9vP72X+TZG2VPs9H2lHKXb/9e97FqbZ2jjCAG X-Received: by 10.200.47.164 with SMTP id l33mr68859691qta.19.1469804629108; Fri, 29 Jul 2016 08:03:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.49.197 with HTTP; Fri, 29 Jul 2016 08:03:48 -0700 (PDT) In-Reply-To: References: <1469627610472-6565.post@n6.nabble.com> <1469787347729-6616.post@n6.nabble.com> From: Semyon Boikov Date: Fri, 29 Jul 2016 18:03:48 +0300 Message-ID: Subject: Re: Deadlock during Client Continuous Query deserialization To: user@ignite.apache.org, dev@ignite.apache.org Content-Type: multipart/alternative; boundary=001a11378e1acebd970538c78eb5 archived-at: Fri, 29 Jul 2016 15:03:54 -0000 --001a11378e1acebd970538c78eb5 Content-Type: text/plain; charset=UTF-8 Here is JIRA issue: https://issues.apache.org/jira/browse/IGNITE-3606 On Fri, Jul 29, 2016 at 5:48 PM, Semyon Boikov 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 > 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. >> > > --001a11378e1acebd970538c78eb5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Fri, J= ul 29, 2016 at 5:48 PM, Semyon Boikov <sboikov@gridgain.com> wrote:
Hi,

<= /div>
I reproduced this issue, thank you for test! After quick debuggin= g It seems that this is some problem with Ignite backpressure mechanism in = communication SPI, I'll create JIRA issue with more details.=C2=A0

As a workaround could you try to disable backpressure:= =C2=A0= tcpCommunicationSpi.setMessageQueueLimit(0);

Thanks!

On Fri, Jul 29, 2016 at 1:15 PM, ross.anderson <ross.anderson@caplin.com> 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 t= o 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-deserializatio= n-tp6565p6616.html
Sent from the Apache Ignite Users mailing list archive at Nabble.= com.


--001a11378e1acebd970538c78eb5--