Hello!
As far as my understanding goes, this is how readThrough work. It may
update only subset of REPLICATED cache partitions across cluster.
Regards,
--
Ilya Kasnacheev
пт, 28 февр. 2020 г. в 21:09, Prasad Bhalerao :
> Hi,
>
> We have not set any expiration/ eviction policy.
> We were
Hi,
We have not set any expiration/ eviction policy.
We were getting false for key "key1", so we checked the key/value by
querying cache using web console and the value is present in cache. But
still getting false for key "key1" on subsequent containskey execution.
But for key "key2" we were
Hi Akash,
Do you execute the cache.contains() method after reading-through the record
with cache.get()? Do you have any expiration/eviction policies set that may
purge the record from memory after being loaded from disk?
-
Denis
On Fri, Feb 28, 2020 at 9:11 AM Akash Shinde wrote:
> Hi,
> I
Hi,
I am using Ignite 2.6 version.
I have partitioned cache, read-through and write-through is enabled.
Back-up count is 1 and total number of server nodes in cluster are 3.
When I try to get the data from a cache for a key using cache.get(key)
method, ignite reads the value from database using
