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

["Vladimir Ozerov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979149#comment-15979149 ] 

Vladimir Ozerov commented on IGNITE-4718:
-----------------------------------------

[~dmagda], one important point - we should properly document deadlock scenarios on standard cache operations, including build operations such as {{putAll}} and {{removeAll}}. We must make sure that this information is highly available to users irrespective of whether they access JavaDocs or wiki. Currently this is mentioned in {{JCache and Beyond}} paragraph [1]. I doubt users read it frequently because of weird naming - no clue that it will contain info on deadlocks :-)

[1] https://apacheignite.readme.io/docs/jcache#section-basic-operations

> 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
>            Assignee: Denis Magda
>             Fix For: 2.1
>
>
> 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)