[IGNITE-4718] Add section in documentation on what actions may cause deadlock

• Type: Task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.8
• Component/s: documentation
• Assignee: Unassigned
• Reporter: Dmitry Karachentsev
• Created: 17/Feb/17 11:41
• Updated: 02/Oct/19 15:46

Description

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.

Issue Links

• is related to: IGNITE-7608 Sort keys in putAll/removeAll methods