eagerTtl

["javastuff.sam@gmail.com" <ja...@gmail.com>]

Hi

I was going through JAVADoc and came across CacheConfiguration property
eagerTtl. Came across one of the post which says eagerTtl=true spans a
thread per cache.
 
We are not using ExpiryPolicy on any of the caches, we have almost 100
different cache. To keep memory and thread footprint down, do we need to
explicitly set eagerTtl=false or with default ExpiryPolicy it is set to
false?

-Sam 



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: eagerTtl

[Denis Magda <dm...@apache.org>]

Val, could put a note regarding this behavior (thread per cache) to both JavaDoc and here?
https://apacheignite.readme.io/docs/expiry-policies

—
Denis

> On Jan 26, 2017, at 5:16 PM, vkulichenko <va...@gmail.com> wrote:
> 
> Surprisingly, the name of the thread is 'ttl-cleanup-worker' :) It's started
> only if there is at least one cache using it.
> 
> -Val
> 
> 
> 
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249p10275.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: eagerTtl

["javastuff.sam@gmail.com" <ja...@gmail.com>]

Thanks, Looks like false alarm. I see a single thread for ttl-cleanup-worker
per node.

-Sam



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249p10292.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: eagerTtl

[vkulichenko <va...@gmail.com>]

Surprisingly, the name of the thread is 'ttl-cleanup-worker' :) It's started
only if there is at least one cache using it.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249p10275.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: eagerTtl

["javastuff.sam@gmail.com" <ja...@gmail.com>]

Hi Val,

JavaDoc does not talk about threads per cache or node. To get more info on
this property, came across below post, I see similar memory and thread
pattern with my application but not yet investigated specifically for
eagerTtl or its related threads.

http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-High-Memory-Overhead-caused-by-GridCircularBuffer-Item-instances-td3682.html#a3691

Can you please point to thread name related to egarTtl which I can take a
look at in thread dump?

Secondly, If none of the cache is configured for expiry, will this thread be
present and running? If it s a single thread per node then I am not worried. 

Thank,
-Sam




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249p10272.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: eagerTtl

[vkulichenko <va...@gmail.com>]

Hi Sam,

According to code, there is actually a thread per node not per cache. Do you
observe different behavior?

Also I didn't find anything about "thread per cache" in JavaDoc. Can you
please show where you read this?

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/eagerTtl-tp10249p10251.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.