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.
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
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
sers.70518.x6.nabble.com/eagerTtl-tp10249p10251.html
Sent from the Apache Ignite Users mailing list archive at Nabble.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
