FYI, same thing happen with IS-4.2.0-ALPHA3,
All my named cached and the default have the following eviction:
<eviction wakeUpInterval="5000" maxEntries="10000" strategy="LIRS" threadPolicy="PIGGYBACK"/>
Any ideas ?
Apologize in advance for bumping this topic but I really would like to solve this as right now all those threads are taking quite some ressources and I am pretty sure that the fix is simple but just happen to evade me for now...
Anyone got an idea of what might happen ? Any leads ?
I believe there is one dedicated thread for eviction per cache no matter what policy you set. Maybe we should revisit this design decision. I'll have a look.
Yep looks like that even with piggyback, a dedicated thread is still allocated to handle expired elements out of the given cache. Ideally when the thread policy is set to piggyback, a common pool shared by all caches should be used to remove expired elements instead of a dedicated one per cache.
Thanks for looking into this !
Thanks Glader and all the devs who participated to the topic here and on the mailing list. Until the issue is adressed, I will look into creating a custom ScheduledExecutorFactory as suggested by Mircea.