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

Posted to issues@ignite.apache.org by "Pavel Pereslegin (JIRA)" <ji...@apache.org> on 2018/03/01 12:54:00 UTC

[jira] [Commented] (IGNITE-7565) Remove IgniteSet from heap

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

Pavel Pereslegin commented on IGNITE-7565:
------------------------------------------

Hello, [~sbberkov].

This issue was raised on devlist and [discussion|http://apache-ignite-developers.2346864.n4.nabble.com/IgniteSet-implementation-changes-required-td23783.html] ended up with the following.
Current implementation is good enough for small sets. As for the large sets we need to implement Set adapter on IgniteCache ([IGNITE-7823|https://issues.apache.org/jira/browse/IGNITE-7823]).

> Remove IgniteSet from heap
> --------------------------
>
>                 Key: IGNITE-7565
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7565
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 2.2
>            Reporter: Alexander Belyak
>            Assignee: Pavel Pereslegin
>            Priority: Major
>
> IgniteSet store all data in durable memory and in java heap. It's not good for big clusters and big sets, so we need to remove values from heap.



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