[IGNITE-7823] Separate cache for non collocated IgniteSet.

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: data structures
• Assignee: Pavel Pereslegin
• Reporter: Andrey Kuznetsov
• Created: 27/Feb/18 11:04
• Updated: 25/Jul/18 13:22
• Resolved: 25/Jul/18 10:57

Description

Currently, single data structures cache is shared between several collection instances (IgniteQueue, IgniteSet).
To support iterator() and size() IgniteSet maintains plain on-heap Java sets on every node (see CacheDataStructuresManager.setDataMap). These sets duplicate backing-cache entries, both primary and backup. For big non-collocated sets it's too expensive to maintain redundant onheap data copies. The simplest way to avoid copies is to use separate cache for non-collocated IgniteSet version; hence size of set is the same as size of backing cache, and also set iterator is virtually the same as backing cache iterator.

The difference between exising set implementation and set based on separate cache should be properly documented afterwards.

Issue Links

• is duplicated by: IGNITE-7565 Remove IgniteSet from heap
• is duplicated by: IGNITE-7564 Document IgniteSet memory consumption
• is related to: IGNITE-640 Implement IgniteMultimap data structures
• is related to: IGNITE-6474 Non-collocated IgniteSet stores duplicate values
• links to: Discussion on devlist.
• links to: GitHub Pull Request #3670
• links to: TC run all.
• links to: Upsource review.