You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/01/23 07:26:05 UTC

[jira] [Resolved] (IGNITE-6411) Add ability to disable WAL for ceratin caches in runtime

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

Vladimir Ozerov resolved IGNITE-6411.
-------------------------------------
    Resolution: Fixed

> Add ability to disable WAL for ceratin caches in runtime
> --------------------------------------------------------
>
>                 Key: IGNITE-6411
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6411
>             Project: Ignite
>          Issue Type: Task
>          Components: persistence
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>            Priority: Major
>              Labels: iep-1, performance
>             Fix For: 2.5
>
>
> Currently every cache update require write to WAL. When doing bulk data load usually crash recovery is not needed. If something went wrong during data load, we should simply purge all intermediate data on cache restart.
> It makes sense to add ability to disable WAL for ceratin caches. Depending on restrictions of current architecture, it could be done on per-cache, per-cache-group or per-memory-policy level.



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