You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/08/31 11:25:45 UTC

[jira] [Created] (IGNITE-1334) Issues with concurrent node stop and cache stop

Semen Boikov created IGNITE-1334:
------------------------------------

             Summary: Issues with concurrent node stop and cache stop
                 Key: IGNITE-1334
                 URL: https://issues.apache.org/jira/browse/IGNITE-1334
             Project: Ignite
          Issue Type: Bug
          Components: cache
            Reporter: Semen Boikov
            Assignee: Semen Boikov
            Priority: Critical
             Fix For: ignite-1.4


There are two issue when cache is destroyed concurrently with node stop:
1. onKernalStop can be called twice for the same cache, it causes hang (for example GridCacheQueryManager.onKernalStop - second attempt to block busyLock which is already blocked will hang).
2. If some exchanges are still in progress GridDhtPartitionsExchangeFutures are completed with error, I see that at least initFut listener created in the 'onReceive(final UUID nodeId, final GridDhtPartitionsFullMessage msg)' does not check initFut result.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)