Re: cache is moved to a read-only state

2019-03-11 Thread Ilya Kasnacheev
Hello! You can't change config, since cache is started its config cannot be changed. Can you share logs from all nodes? Regards, -- Ilya Kasnacheev пн, 11 мар. 2019 г. в 13:11, Aat : > No - All my servers was available. > I change cache config. > > > > -- > Sent from:

Re: cache is moved to a read-only state

2019-03-11 Thread Aat
No - All my servers was available. I change cache config. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: cache is moved to a read-only state

2019-03-11 Thread Ilya Kasnacheev
Hello! As far as I can see this should happen if you lose two server nodes at the same time. Did this happen? Regards, -- Ilya Kasnacheev пт, 8 мар. 2019 г. в 18:46, Aat : > visor> cache -slp -c=marketData > Lost partitions for cache: marketData (12) >

Re: cache is moved to a read-only state

2019-03-08 Thread Aat
visor> cache -slp -c=marketData Lost partitions for cache: marketData (12) +=+ | Interval |Partitions| +=+ | 86-816 | 86, 115, 241, 469,

Re: cache is moved to a read-only state

2019-03-08 Thread Aat
"Failed to write to cache (cache is moved to a read-only state): " + cctx.name()); } and in my config i setted : .setPartitionLossPolicy(READ_ONLY_ALL) /** * All writes to the cache will be failed with an exception. All reads will proceed as if

Re: cache is moved to a read-only state

2019-03-08 Thread Aat
dException: Failed to write to cache (cache is moved to a read-only state): marketData 3 at org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1337) 4 at org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cach

cache is moved to a read-only state

2019-03-08 Thread Aat
Hello, after 5 minutes i have this exception : 2541 javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to write to cache (cache is moved to a read-only state): marketData 2542