ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-7010) Ignite hangs on cache destroy called from IgniteBiPredicate - Ignite Events
Date Fri, 24 Nov 2017 10:05:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew Mashenkov resolved IGNITE-7010.
    Resolution: Not A Bug

Synchronous cache.destroy() call in listener is delay current topology changing procedure
until it has finished with no success of course.

> 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 ({code}ignite.destroyCache("testCache"){code})
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

View raw message