You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Krzysztof Chmielewski (JIRA)" <ji...@apache.org> on 2017/11/24 08:28:00 UTC
[jira] [Created] (IGNITE-7010) Ignite hangs on cache destroy called
from IgniteBiPredicate - Ignite Events
Krzysztof Chmielewski created IGNITE-7010:
---------------------------------------------
Summary: Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
Key: IGNITE-7010
URL: https://issues.apache.org/jira/browse/IGNITE-7010
Project: Ignite
Issue Type: Bug
Affects Versions: 2.3
Reporter: Krzysztof Chmielewski
Ignite hangs trying to delete cache as a response to Ignite Event EventType.EVT_NODE_LEFT.
Code to reproduce this issue is available at https://github.com/kristoffSC/IgniteHang
Reproduce instructions:
# Put break points in ServerStarter.java line 40 and 42.
## Start ServerStarter as Java Application in Debug mode.
### Start ClientStarter as Java Application. After ClientStarter ends, ServerStarter detects EventType.EVT_NODE_LEFT and will stops at line 40 (BP). Try skip to next line (ignite.destroyCache("testCache");) and then try skip one more line. Ignite will hang at line 41.
This "hang" prevents other nodes from connecting to this running/hanging Ignite Server.
Thread that stuck is "disco-event-worker". It waits on {code} return stopFut.get() {code} in IgniteKernel.class at line 3146
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)