ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9290) Make remove explicit locks async when node left.
Date Thu, 16 Aug 2018 08:27:00 GMT

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

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

GitHub user AMashenkov opened a pull request:

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

    IGNITE-9290: Make remove explicit locks async when node left.

    

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

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

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

    https://github.com/apache/ignite/pull/4556.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 #4556
    
----
commit 5190f178898ca25a71cd1b7be5efec71ef39a827
Author: Andrey V. Mashenkov <andrey.mashenkov@...>
Date:   2018-08-15T09:52:08Z

    Cleanup code.
    
    Remove unused method parameter.

commit 7602100c68bd177d93a9a8d12df7ddb397efc77f
Author: Andrey V. Mashenkov <andrey.mashenkov@...>
Date:   2018-08-15T09:53:01Z

    Make explicit locks removal async.

----


> Make remove explicit locks async when node left.
> ------------------------------------------------
>
>                 Key: IGNITE-9290
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9290
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>            Priority: Major
>
> GridCacheMvccManager.removeExplicitNodeLocks() run synchronously in discovery and exchange threads.
This introduce unnecessary delays in discovery 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), as manager stops right
after last exchange has finished so managers can't detect node is stopping. 
>  
> [1] [http://apache-ignite-developers.2346864.n4.nabble.com/Synchronous-tx-entries-unlocking-in-discovery-exchange-threads-td33827.html] 



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

Mime
View raw message