>
> I've got a reproducer that can be related. See comments
> http://apache-ignite-users.70518.x6.nabble.com/Partition-eviction-failed-
> this-can-cause-grid-hang-Caused-by-java-lang-
> IllegalStateException-Failed--tp19122p20524.html
>
> Sergey Sergeev, just for reference,
Hi Mikhail,
Unfortunately, the problem has repeated itself on ignite-core-2.3.3
27.02.18 00:27:55 ERROR GridCacheIoManager - Failed to process message
[senderId=8f99c887-cd4b-4c38-a649-ca430040d535, messageType=class
o.a.i.i.processors.cache.distributed.dht.atomic.
GridNearAtomicUpdateResponse]
Hi Igniters
I can't defeat the bug. It is reproducing on ignite version community 2.3.0
and on trial professional 2.3.2 editions.
The Cache has configuration like:
final CacheConfiguration cacheConfiguration
= new CacheConfiguration<>(getEntityClass().getSimpleName());
cacheConfiguration.setCac
rations?
>
> Yes, you can have the persistence enabled for region A and disabled for
> region B.
>
> —
> Denis
>
>
> > On Dec 22, 2017, at 1:13 PM, Sergey Sergeev
> wrote:
> >
> > Hi,
> >
> > I'm confused. After the successful launch of
Hi,
I'm confused. After the successful launch of the Ignite cluster version
2.3.0, I saw the WARN message:
WARN GridCacheDatabaseSharedManager - Page eviction mode for [inMemory]
memory region is ignored because Ignite Native Persistence is enabled
Ignite spring config see below:
...
