[jira] [Updated] (IGNITE-7823) Separate cache for non collocated IgniteSet.

["Pavel Pereslegin (JIRA)" <ji...@apache.org>]

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

Pavel Pereslegin updated IGNITE-7823:
-------------------------------------
    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 sets it's too expensive to maintain redundant onheap data copies. Thus it would be better to use separate cache for non collocated IgniteSet version. The difference between these two kinds of sets should be properly documented afterwards.

  was:
Existing collocated version of {{IgniteSet}} datastructure is good enough for small sets.
For big sets it's too expensive to maintain redundant onheap data copies. Thus it would be better to use separate cache for non collocated {{IgniteSet}} version. The difference between these two kinds of sets should be properly documented afterwards. 


> Separate cache for non collocated IgniteSet.
> --------------------------------------------
>
>                 Key: IGNITE-7823
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7823
>             Project: Ignite
>          Issue Type: New Feature
>          Components: data structures
>            Reporter: Andrey Kuznetsov
>            Assignee: Pavel Pereslegin
>            Priority: Major
>             Fix For: 2.6
>
>
> 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 sets it's too expensive to maintain redundant onheap data copies. Thus it would be better to use separate cache for non collocated IgniteSet version. The difference between these two kinds of sets should be properly documented afterwards.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)