ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Scherbakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4429) Deadlock in IgniteAtomicSequence when used inside transaction
Date Wed, 14 Dec 2016 16:40:58 GMT

    [ 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)

Mime
View raw message