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

Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/04/09 14:08:00 UTC

[jira] [Updated] (IGNITE-5286) Reconsider deferredDelete implementation

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

Alexey Goncharuk updated IGNITE-5286:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> Reconsider deferredDelete implementation
> ----------------------------------------
>
>                 Key: IGNITE-5286
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5286
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.6
>
>
> In current implementation entries marked for 'deferredDelete' should be stored on heap (otherwise information about remove is lost). This potentially can be an issue if there are a lot of removes.
> (note: in current 'deferredDelete' implementation in Ignite there is a bug - https://issues.apache.org/jira/browse/IGNITE-3299).



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