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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:02:02 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 ]

Maxim Muzafarov updated IGNITE-5286:
------------------------------------
    Fix Version/s:     (was: 2.8)
                   2.9

> 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.9
>
>
> 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
(v8.3.4#803005)