Hello!
As far as my understanding goes, each cache operation has a chance of
expiring some number of cache entries, so the answer is "e1 and e2 may be
removed when putting e3 into mycache".
Maybe there's somebody to correct me.
Regards,
--
Ilya Kasnacheev
ср, 24 февр. 2021 г. в 09:36, xmw4568
Excepted from the latest Ignite doc -
"If the property (eagerTtl) is set to false, expired entries are not removed
immediately. Instead, they are removed when they are requested in a cache
operation by the thread that executes the operation."
Say mycache has two entries, e1, e2 with 5 min crea
Thanks Nikolai.
On Mon, Apr 3, 2017 at 7:05 PM, Nikolai Tikhonov
wrote:
> Hi,
>
> "When entry accessed" is mind that entry will be involved by IgniteCache
> API (put/get/invoke and etc). In during operation ttl will be checked.
>
> Ignite SQL doesn't update ttl and entry won't be removed.
>
>
>
Hi,
"When entry accessed" is mind that entry will be involved by IgniteCache
API (put/get/invoke and etc). In during operation ttl will be checked.
Ignite SQL doesn't update ttl and entry won't be removed.
On Mon, Apr 3, 2017 at 4:28 PM, Tolga Kavukcu
wrote:
> Hi Everyone,
>
> I have a questi
Hi Everyone,
I have a question about cache ttl. I understand that when eager ttl is set
to true for a cache, a thread created and expired entries are cleaned but
this can cause some heap usage.
Otherwise i can set eager ttl to false, when entry accessed ignite checks
if entry expired or not it is
