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 order to regularly clean up the cache I decided to implement time based and state based eviction on the cache. For time based eviction I used cache.setExpiryPolicyFactory(). State based eviction is implemented by a service that deletes an entry from the cache as soon as a certain field has reached a final state. I experience the following problem: Sometimes the state changes faster than write behind, hence the final state of my cache entry will not be written behind to the DB. Thus my questions: - Is there any way to programmatically trigger a write behind on a cache? - Is there maybe any Ignite internal option of marking a cache entry as expired as soon as a certain state is reached? - Will the ExpiryPolicy take into account the configured write-behind? Meaning, will it trigger a write behind before deleting the entry if it has not been written into the DB before?
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
