Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4A50F1825D for ; Mon, 11 Jan 2016 15:09:40 +0000 (UTC) Received: (qmail 52667 invoked by uid 500); 11 Jan 2016 15:09:40 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 52599 invoked by uid 500); 11 Jan 2016 15:09:40 -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 52546 invoked by uid 99); 11 Jan 2016 15:09:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2016 15:09:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DCA8A2C14F7 for ; Mon, 11 Jan 2016 15:09:39 +0000 (UTC) Date: Mon, 11 Jan 2016 15:09:39 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-1321) Revisit PlatformAbstractTask locking logic. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1321: ------------------------------------ Fix Version/s: (was: 1.6) > Revisit PlatformAbstractTask locking logic. > ------------------------------------------- > > Key: IGNITE-1321 > URL: https://issues.apache.org/jira/browse/IGNITE-1321 > Project: Ignite > Issue Type: Task > Components: interop > Affects Versions: 1.1.4 > Reporter: Vladimir Ozerov > Assignee: Vladimir Ozerov > > Currently it is implemented with RW lock to ensure that task cannot be cancelled/completed concurrently when notie platform process job result. > This was done when we were dealing with non-unique native pointers. > Now this is not a problem because we use "handle registry" approach and all "pointers" are guaranteed to be unique. Therefore, probably we can get rid of this lock at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)