You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/19 19:28:00 UTC

[jira] [Commented] (IGNITE-9147) Race between tx async rollback and lock mapping on near node can produce hanging primary tx

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

ASF GitHub Bot commented on IGNITE-9147:
----------------------------------------

GitHub user ascherbakoff opened a pull request:

    https://github.com/apache/ignite/pull/4574

    IGNITE-9147 Race between tx async rollback and lock mapping on near node can produce hanging primary tx.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9147

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4574.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4574
    
----
commit d67d235fab6b754b4fba35ff139d8edbf4af614f
Author: ascherbakoff <al...@...>
Date:   2018-08-19T19:22:26Z

    IGNITE-9147 wip.

----


> Race between tx async rollback and lock mapping on near node can produce hanging primary tx
> -------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-9147
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9147
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 2.5
>            Reporter: ARomantsov
>            Assignee: Alexei Scherbakov
>            Priority: Critical
>             Fix For: 2.7
>
>
> I ran a simple test
> 1) Start 15 servers node
> 2) Start client with long transaction
> 3) Additional start 5 client with loading in many caches (near 2 thousand)
> 4) Stop 1 server node, wait 1 minute and start it back
> Cluster freenze on more than hour



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)