Hello!
You may
call
org.apache.ignite.internal.processors.cache.store.GridCacheWriteBehindStore#forceFlush
when deciding to evict some entries, assuming you are doing it manually.
Regards,
--
Ilya Kasnacheev
ср, 9 июн. 2021 г. в 11:21, r_s :
> Hello All,
> I am running a partitioned cache wi
Hi Alexey,
thank you for your answer, this confirms what I expected.
For clarification: I do not want my DB to evict any entries, I just want to
make sure alle updates on the cache entries are written before the entries
are removed from the cache.
I have not designed the architecture of native
Cache expiry policy evicts entries only from the cache and native
persistent store: the external DB is not modified. So your expiry policy
has nothing to do with write-behind.
If you want to evict entries from both the cache and external DB you may
consider implementing such a policy as a replicat
Hello All,
I am running a partitioned cache with native persistence and write-behind to
a DB. Because the DB is fairly slow, I decided to use write-behind not
write-through. Out of many, mainly performance reasons it makes sense to
also use native persistence instead of only in memory caching.
In o
