Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 14 Dec 2016 16:40:58 +0000 (UTC)
From: "Alexei Scherbakov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13028102.1481724810000.520899.1481733658585@Atlassian.JIRA>
In-Reply-To: <JIRA.13028102.1481724810000@Atlassian.JIRA>
References: <JIRA.13028102.1481724810000@Atlassian.JIRA> <JIRA.13028102.1481724810692@arcas>
Subject: [jira] [Commented] (IGNITE-4429) Deadlock in IgniteAtomicSequence
 when used inside transaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 14 Dec 2016 16:41:00 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15748803#comment-15748803 ] 

Alexei Scherbakov commented on IGNITE-4429:
-------------------------------------------

WIth the new separation of system and user transaction the fix as simple as removing outTx call.

PR: https://github.com/apache/ignite/pull/1347

Scheduled TC run.

> Deadlock in IgniteAtomicSequence when used inside transaction
> -------------------------------------------------------------
>
>                 Key: IGNITE-4429
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4429
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, compute, data structures
>            Reporter: Alexei Scherbakov
>            Assignee: Alexei Scherbakov
>             Fix For: 2.0
>
>
> On certains scenarios involving job runs using compute API, operations with {{IgniteAtomicSequence}} inside user transactions may lead to deadlock caused by public thread pool exhaustion.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)