You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergei Ryzhov (Jira)" <ji...@apache.org> on 2019/10/12 16:54:00 UTC
[jira] [Commented] (IGNITE-8473) Add option to enable/disable WAL
for several caches with single command
[ https://issues.apache.org/jira/browse/IGNITE-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950090#comment-16950090 ]
Sergei Ryzhov commented on IGNITE-8473:
---------------------------------------
https://github.com/apache/ignite/pull/6971
> Add option to enable/disable WAL for several caches with single command
> -----------------------------------------------------------------------
>
> Key: IGNITE-8473
> URL: https://issues.apache.org/jira/browse/IGNITE-8473
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Rakov
> Assignee: Sergei Ryzhov
> Priority: Major
> Labels: newbie
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> API method for disabling WAL in IgniteCluster accepts only one cache name. Every call triggers exchange and checkpoints cluster-wide - it takes plenty of time to disable/enable WAL for multiple caches.
> We should add option to disable/enable WAL for several caches with single command.
> New proposed API methods:
> {noformat}
> IgniteCluster.disableWal(Collection<String> cacheNames)
> IgniteCluster.enableWal(Collection<String> cacheNames)
> IgniteCluster.disableWal() // Disables WAL for all caches.
> IgniteCluster.enableWal() // Enables WAL for all caches.
> {noformat}
> Methods should return true if WAL state of at least one cache was actually changed by the call.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)