Write ahead log and early eviction of new elements

[Raymond Wilson]

I have a scenario I would like to validate when using Ignite Persistence.



I understand when I add an element to a cache that element is serialized,
placed into the local memory for the cache on that server and then placed
into the WAL pending checkpointing (merging into the persistence store).



What happens if the newly added element is evicted and then re-read from
the cache by the client before the next checkpoint occurs?



Thanks,

Raymond.

[dmagda]

My guess before the entry (element) gets evicted it will be synced to a respective partition file on disk forcibly so that you can grab it from there later.

Ignite persistence experts please confirm my understanding.

—
Denis

> On Feb 13, 2018, at 1:28 PM, Raymond Wilson <[hidden email]> wrote:
>
> I have a scenario I would like to validate when using Ignite Persistence.
>  
> I understand when I add an element to a cache that element is serialized, placed into the local memory for the cache on that server and then placed into the WAL pending checkpointing (merging into the persistence store).
>  
> What happens if the newly added element is evicted and then re-read from the cache by the client before the next checkpoint occurs?
>  
> Thanks,
> Raymond.
>