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 AED1A200CBC for ; Tue, 20 Jun 2017 18:28:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AD7CD160BEF; Tue, 20 Jun 2017 16:28:07 +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 002EA160BD3 for ; Tue, 20 Jun 2017 18:28:06 +0200 (CEST) Received: (qmail 97063 invoked by uid 500); 20 Jun 2017 16:28:06 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 97054 invoked by uid 99); 20 Jun 2017 16:28:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jun 2017 16:28:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D260DC043B for ; Tue, 20 Jun 2017 16:28:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id VQbfmnagYSE9 for ; Tue, 20 Jun 2017 16:28:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8EC2B610C8 for ; Tue, 20 Jun 2017 16:28:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6BA98E0D48 for ; Tue, 20 Jun 2017 16:28:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 568AA24091 for ; Tue, 20 Jun 2017 16:28:00 +0000 (UTC) Date: Tue, 20 Jun 2017 16:28:00 +0000 (UTC) From: "Alexander Menshikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-4365) Data grid in deadlock on stop MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 20 Jun 2017 16:28:07 -0000 [ https://issues.apache.org/jira/browse/IGNITE-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056043#comment-16056043 ] Alexander Menshikov commented on IGNITE-4365: --------------------------------------------- [~yzhdanov] I don't see any onExchangeFinish() methods. There is not in thread dumb and even in all projects. Only GridCacheProcessor#onExchangeDone() looks similar. Do you mean this method? Anyway, am I right the problem is GridCacheGateway#onStopped() is waiting for unlocking of all locks, but other threads don't know about a stopping processes? And make it clear for me please: is the main way to solve the problem of sending a signal to the other threads about the beginning of the process of stopping? And we shouldn't fight with deadlocks, but we should add a mechanism for abort work under locks? > Data grid in deadlock on stop > ----------------------------- > > Key: IGNITE-4365 > URL: https://issues.apache.org/jira/browse/IGNITE-4365 > Project: Ignite > Issue Type: Bug > Components: cache > Reporter: Yakov Zhdanov > Labels: busylock, gateway, performance > Attachments: thread-dump.txt > > > Attached is the threaddump describing the problem. > # several public threads wait for new cache topology version > # onExchangeFinish() tries to stop the gateway, but cannot do it due to public threads waiting inside the GW. > # grid stopping thread waits for job requests to complete -- This message was sent by Atlassian JIRA (v6.4.14#64029)