Hi Mikalai! We faced the same problem. I created a "reproducer" and filled a ticket [1]. I did an initial analysis and from my point of view, the problem is in the incorrect exception handling (detailed description inside the ticket) without impact. I plan to look into the issue in more detail and fix it soon.
[1] https://issues.apache.org/jira/browse/IGNITE-16118 пт, 25 февр. 2022 г. в 17:45, Mikalai Churakou (c) <mchura...@vmware.com>: > > Hello, dev Apache Ignite team > > Could you be so kind and assist with described below issue? > > Thanks, Mikalai > > Begin forwarded message: > > From: Mikalai Churakou (c) <mchura...@vmware.com<mailto:mchura...@vmware.com>> > Subject: Failed to send TTL update request > Date: 21 February 2022 at 21:49:53 GMT+3 > To: u...@ignite.apache.org<mailto:u...@ignite.apache.org> > Cc: Amit Kapoor <amkap...@vmware.com<mailto:amkap...@vmware.com>>, Ivaylo > Pankov <pank...@vmware.com<mailto:pank...@vmware.com>> > > Hello, dear Ignite representatives > > Our team supports app which uses Apache Ignite > (org.apache.ignite:ignite-core:2.10.0) for cache functionality. > We have enabled hibernate l2 cache feature for few entities and configured > cache regions for them plus 2 regions (query cache and update timestamp > region). > In configurations we have expiration policies: 1 or 7 days. > After that we observe in logs exceptions for introduced cache regions: > > <${region name}> Failed to send TTL update request > > org.apache.ignite.internal.processors.cache.GridCacheEntryRemovedException: > null > at > org.apache.ignite.internal.processors.cache.GridCacheMapEntry.checkObsolete(GridCacheMapEntry.java:3066) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.checkReadersLocked(GridDhtCacheEntry.java:732) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.checkReaders(GridDhtCacheEntry.java:708) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.readers(GridDhtCacheEntry.java:416) > at > org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter$8.run(GridDhtCacheAdapter.java:1134) > at > org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7141) > at > org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:829) > at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:829) > > Could you assist with understanding of the issue and impact of such > exceptions? It would be nice to have ideas about possible > solution/workarounds? > > Thanks, Mikalai >
