From issues-return-87804-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jan 11 15:51:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E0AA6180648 for ; Fri, 11 Jan 2019 15:51:03 +0100 (CET) Received: (qmail 5917 invoked by uid 500); 11 Jan 2019 14:51:03 -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 5905 invoked by uid 99); 11 Jan 2019 14:51:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2019 14:51:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B6E3F1805DE for ; Fri, 11 Jan 2019 14:51:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.188 X-Spam-Level: X-Spam-Status: No, score=-108.188 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URI_HEX=1.313, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id I0gpze-_G9AQ for ; Fri, 11 Jan 2019 14:51:01 +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 027F160DB3 for ; Fri, 11 Jan 2019 14:51:01 +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 85BB7E2642 for ; Fri, 11 Jan 2019 14:51:00 +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 34C242558C for ; Fri, 11 Jan 2019 14:51:00 +0000 (UTC) Date: Fri, 11 Jan 2019 14:51:00 +0000 (UTC) From: "Alexey Goncharuk (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-9290) Make remove explicit locks async when node left. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-9290?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D167= 40456#comment-16740456 ]=20 Alexey Goncharuk commented on IGNITE-9290: ------------------------------------------ [~amashenkov], I've re-checked, since we do not submit the task to the stri= ped pool, nothing else should be changed. Thanks, merged to master. > Make remove explicit locks async when node left. > ------------------------------------------------ > > Key: IGNITE-9290 > URL: https://issues.apache.org/jira/browse/IGNITE-9290 > Project: Ignite > Issue Type: Bug > Components: cache > Reporter: Andrew Mashenkov > Assignee: Andrew Mashenkov > Priority: Critical > Labels: deadlock, iep-25 > Fix For: 2.8 > > > GridCacheMvccManager.removeExplicitNodeLocks() run synchronously in disco= very and exchange=C2=A0threads. This introduce unnecessary delays in discov= ery and exchange process. > Also, this may cause a deadlock on node stop if user transaction holds an= entry lock and awaits some Ignite manager response (e.g. cache store or DR= or CQ), as=C2=A0manager stops right after last exchange has finished so ma= nagers can't detect node is stopping.=C2=A0 > =C2=A0 > [1]=C2=A0[http://apache-ignite-developers.2346864.n4.nabble.com/Synchrono= us-tx-entries-unlocking-in-discovery-exchange-threads-td33827.html]=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)