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

Ivan Rakov updated IGNITE-8473:
-------------------------------
    Description: 
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()
IgniteCluster.enableWal()
{noformat}
Methods should return true if WAL state of at least one cache was actually 
changed by the call.

  was:
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:
IgniteCluster.disableWal(Collection<String> cacheNames)
IgniteCluster.enableWal(Collection<String> cacheNames)
IgniteCluster.disableWal()
IgniteCluster.enableWal()

Methods should return true if WAL state of at least one cache was actually 
changed by the call.


> 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
>            Priority: Major
>             Fix For: 2.6
>
>
> 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()
> IgniteCluster.enableWal()
> {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
(v7.6.3#76005)

Reply via email to