Hi, This is a correct behavior, by design any cache evictions and expirations don't affect store, because cache usually keeps only hot data. If you set read though, then Ignite will request store in case if entry wasn't found in cache, otherwise it returns null and to load that data back in cache you need to call IgniteCache.loadCache().
Write through writes any cache changes into database immediately, but write behind does it in background, that significantly increases performance. Thanks! -Dmitry. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Expired-entry-in-cache-with-persistent-store-tp13156p13354.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
