"Write behind" is a feature of "write through", but when the feature was
used the entries will written asynchronously.
Hence If all entries hit into storage it is correct behavior.

Please provide reproduced example, If are you means another?

On Sat, Oct 8, 2016 at 11:00 PM, Pradeep Badiger <pradeepbadi...@fico.com>

> Hi,
> I am trying to evaluate Apache Ignite and trying to explore eviction
> policy and write behind features. I am seeing that whenever a cache is
> configured with eviction policy and write behind feature, the write behind
> cache always have all the changed entries including the ones that are
> evicted, before the write cache is flushed. But soon after it is flushed,
> the store loads again from DB. Is this the expected behavior? Is there a
> documentation on how the write behind cache works?
> Thanks,
> Pradeep V.B.
> This email and any files transmitted with it are confidential, proprietary
> and intended solely for the individual or entity to whom they are
> addressed. If you have received this email in error please delete it
> immediately.

Vladislav Pyatkov

Reply via email to