ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Voronkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10511) disco-event-worker can be deadlocked by BinaryContext.metadata running is sys striped pool waiting for cache entry lock
Date Wed, 05 Dec 2018 09:14:00 GMT

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

Pavel Voronkin commented on IGNITE-10511:
-----------------------------------------

Closing as duplicate.

> disco-event-worker can be deadlocked by BinaryContext.metadata running is sys striped
pool waiting for cache entry lock
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-10511
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10511
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Pavel Voronkin
>            Priority: Major
>         Attachments: race.txt
>
>
> See attached thread dump:
> disco-event-worker hangs on removeExplicitNodeLocks() on GridCacheMapEntry which is
held by GridDistributedTxRemoteAdapter acquired in GridCacheMapEntry.innerSet().
> CacheObjectBinaryProcessorImpl is waiting on metadata message on discovery, which can
be processed due to disco-event-worker is stuck.
> Possible fix:
> {code:java}
>     public void onNodeLeft(final ClusterNode node) {
>         if (isDone() || !enterBusy())
>             return;
>         cctx.mvcc().removeExplicitNodeLocks(node.id(), initialVersion());
>         try {
>             onDiscoveryEvent(new IgniteRunnable() {
>                  @Override public void run() {
>                      if (isDone() || !enterBusy())
>                          return;
>                      
>                      ...
>                  }
>              });
>         }
>         finally {
>             ...
>         }
>     }
> {code}
> As we can see most of the processing is done async in IgniteRunnable() in exchange-worker.
>  
> We can move 
> {code:java}
>     cctx.mvcc().removeExplicitNodeLocks(node.id(), initialVersion());
> {code}
> inside this Runnable's body.



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

Mime
View raw message