You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/10/15 08:39:01 UTC
[jira] [Commented] (IGNITE-9290) Make remove explicit locks async
when node left.
[ https://issues.apache.org/jira/browse/IGNITE-9290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649897#comment-16649897 ]
Andrew Mashenkov commented on IGNITE-9290:
------------------------------------------
[~NIzhikov], sorry, I've missed your last message.
The ticket is on review stage since I've asked for review at 23 Aug on dev list [1].
Now, it looks targeted to the next 2.8 release. Most likely, PR contains changes on critical path and need to be reviewed very carefully that may takes a time.
I've merged PR with latest master to resolve conflicts.
[1] http://apache-ignite-developers.2346864.n4.nabble.com/Synchronous-tx-entries-unlocking-in-discovery-exchange-threads-td33827.html
> Make remove explicit locks async when node left.
> ------------------------------------------------
>
> Key: IGNITE-9290
> URL: https://issues.apache.org/jira/browse/IGNITE-9290
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Critical
> Labels: deadlock, iep-25
> Fix For: 2.8
>
>
> 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 or CQ), 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)