ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-1221) Proper GridCacheContext cleanup
Date Mon, 10 Aug 2015 12:04:45 GMT
Denis Magda created IGNITE-1221:

             Summary: Proper GridCacheContext cleanup
                 Key: IGNITE-1221
                 URL: https://issues.apache.org/jira/browse/IGNITE-1221
             Project: Ignite
          Issue Type: Bug
          Components: cache
            Reporter: Denis Magda
            Priority: Critical

Sometimes when a cache is stopped and its corresponding {{GridCacheContext}} is cleaned up
there are some threads exist that keep executing cache related operations.

This may lead to deadlocks, hangs and other unpredictable results.

Initial discussion on the dev list:
Look for discussion "Fixed deadlock in GridDhtAtomicCache (Alex G. your review is needed)"

As an example, the bug described and fixed as IGNITE-1189 was caused by already invalidated

Moreover, Andrey Gura reports that he observes hangs in cache's read operations probably caused
by the same reason.

To reproduce try to do the following.

Temporary comment out the following catch block in {{GridDhtAtomicCache.updateAllAsyncInternal0}}:
        catch (Exception e) {
            // At least RuntimeException can be thrown by the code above when GridCacheContext
is cleaned and there is
            // an attempt to use cleaned resources.
            U.error(log, "Unexpected exception during cache update", e);

            res.addFailedKeys(keys, e);

            completionCb.apply(req, res);


Run {{IgniteCacheAtomicNodeRestartTest.testRestartWithPutTenNodesTwoBackups}} in a loop using

This message was sent by Atlassian JIRA

View raw message