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.
