You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (JIRA)" <ji...@apache.org> on 2018/08/28 13:33:00 UTC
[jira] [Updated] (IGNITE-8309) Cannot change WAL mode from client
node
[ https://issues.apache.org/jira/browse/IGNITE-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Kasnacheev updated IGNITE-8309:
------------------------------------
Fix Version/s: (was: 2.7)
> Cannot change WAL mode from client node
> ---------------------------------------
>
> Key: IGNITE-8309
> URL: https://issues.apache.org/jira/browse/IGNITE-8309
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.5
> Reporter: Ilya Kasnacheev
> Assignee: Vladimir Ozerov
> Priority: Major
>
> I have cluster of a few nodes with persistence region, and a few clients, obviously without persistence region.
> When I try to do disableWal(cacheName) on client node, I observe the following exception:
> {code}
> Caused by: org.apache.ignite.IgniteCheckedException: Cannot change WAL mode because persistence is not enabled for cache(s) [caches=[data0], dataRegion=null]
> at org.apache.ignite.internal.processors.cache.WalStateManager.errorFuture(WalStateManager.java:759) ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at org.apache.ignite.internal.processors.cache.WalStateManager.init(WalStateManager.java:292) ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at org.apache.ignite.internal.processors.cache.GridCacheProcessor.changeWalMode(GridCacheProcessor.java:3045) ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> {code}
> From server node I can disable and enable WAL without problems. Since it's a cluster-wide operations, I expect it to be doable from client also.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)