RE: Re: Cache entries expiring in pageEvictionMode=DISABLED

[Alexandr Shapkin]

>What's worse - they are evicted on one node, and eviction >is not propagated on the other two nodes (so now every node has different >count of entries for that cache, even though it's replicated)   Data region configuration defines a local machine’s memory settings, it doesn’t propagate to other nodes.   Have you managed to get the eviction work properly?   From: akorensh Sent: Wednesday, January 15, 2020 11:36 PM To: user@ignite.apache.org Subject: Re: Cache entries expiring in pageEvictionMode=DISABLED   Hi,   Are you not seeing cache entries and therefore making the assumption that eviction has kicked in? You could inadvertently be using a different config w/persistence turned on?   search in ignite logs for the words "persistenceEnabled=false"   If you've not enabled onHeapCaching or persistence, and page eviction is disabled and no memory is left, Ignite will throw IgniteOutOfMemoryException.   docs for your version: https://apacheignite.readme.io/v2.3/docs/evictions   Can you try with only one cache(NonEvictable_256MB_Region) and see whether the problem repeats itself?   Also, you have an old version, and if possible, can you do a small test using a newer version(2.7.6) https://ignite.apache.org/download.cgi  and see whether the behavior repeats itself.   If you are able to reproduce this on 2.7.6, then send us your entire config, a reproducer project (or the code that you use to populate the cache) and we will take a look.   Thanks, Alex       -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/