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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/02 15:47:02 UTC

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

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

Maxim Muzafarov updated IGNITE-4718:
------------------------------------
    Fix Version/s:     (was: 2.8)

> 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
>          Components: documentation
>    Affects Versions: 1.8
>            Reporter: Dmitry Karachentsev
>            Priority: Minor
>
> 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
(v8.3.4#803005)