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

["Ilya Kasnacheev (JIRA)" <ji...@apache.org>]

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

Ilya Kasnacheev commented on IGNITE-6411:
-----------------------------------------

Alternatively, it may make sense to be able to flush & fsync WAL manually.

If updates are done in batch fashion, it doesn't make sense to crash recover the middle of batch, but it makes total sense to provide guarantees that batches are ingested properly and cannot be lost.

I was thinking of LOG_ONLY WAL mode with manual flush & fsync.

> 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
>              Labels: iep-1, performance
>
> 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
(v6.4.14#64029)