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

Posted to dev@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2017/02/17 11:42:41 UTC

[jira] [Created] (IGNITE-4718) Add section in documentation on what actions may cause deadlock

Dmitry Karachentsev created IGNITE-4718:
-------------------------------------------

             Summary: Add section in documentation on what actions may cause deadlock
                 Key: IGNITE-4718
                 URL: https://issues.apache.org/jira/browse/IGNITE-4718
             Project: Ignite
          Issue Type: Task
    Affects Versions: 1.8
            Reporter: Dmitry Karachentsev


Ignite has number of common cases, where wrong usage of API may lead to deadlocks, starvations, cluster hangs, and they should be properly documented. 

For example, cache operations is not allowed in CacheEntryProcessor, ContinuousQuery's remote filter, etc. And in some callbacks it's possible to use cache API if they annotated with @IgniteAsyncCallback.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)