[ https://issues.apache.org/jira/browse/IGNITE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277373#comment-16277373 ]
ASF GitHub Bot commented on IGNITE-6411: ---------------------------------------- GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3137 IGNITE-6411 WIP Signed-off-by: Anton Vinogradov <a...@apache.org> You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7003 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3137.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3137 ---- commit ec58473bfce5ec28b8710b98e733a23ef38bbfaa Author: Anton Vinogradov <a...@apache.org> Date: 2017-12-04T19:45:31Z IGNITE-6411 WIP Signed-off-by: Anton Vinogradov <a...@apache.org> ---- > 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 > Assignee: Anton Vinogradov > Labels: iep-1, performance > Fix For: 2.4 > > > 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)