Re: Ensuring CacheStore Operations Finished

I've checked some details and found out that Cache.destroy future will be completed only after all changes are flushed to a persistent storage. This way Cache.destroy() call completes when synchronization is already finished. Best Regards, Roman -- Sent from:

Re: Ensuring CacheStore Operations Finished

Hi Roman. We use write-behind for performance considerations. We cannot use write-through for that reason. Regards. On Wed, Apr 18, 2018 at 9:59 AM, Roman Guseinov wrote: > Hi Alper, > > To make sure that all cache changes propagated to 3rd Party Persistence > please

Re: Ensuring CacheStore Operations Finished

Hi Alper, To make sure that all cache changes propagated to 3rd Party Persistence please enable Write-Through option [1] and disable Write-Behind. Write-through means that the data will be automatically persisted whenever it is updated in the cache. Best Regards, Roman [1]

Ensuring CacheStore Operations Finished

Hi all. My use case is as follows: - Create a cache A that synchronizes with DB table A_TABLE - Destroy A and backup A_TABLE as A_TABLE_BCK At the moment between destroy and backup is there a way to know that all the synchronization was finished and the A_TABLE is not incomplete? Regards. --