Hi, In our project, we have an Ignite 2 based cache, configured with an LRU eviction policy. We are now migrating to Ignite 3 and would like to preserve the same operating principle. We were expecting that the possibility of configuring an eviction policy would be maintained in Ignite 3, for an in-memory cache solution.
Best regards, Pedro Rocha ________________________________ From: Jeremy McMillan <[email protected]> Sent: Monday, January 5, 2026 19:01 To: [email protected] <[email protected]> Cc: Pedro Rocha (Nokia) <[email protected]> Subject: Re: AiMem profile storage engine eviction You don't often get email from [email protected]. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Ignite 3 isn't really a cache. Also the Ignite 2 eviction strategies were always a compromise from what people really wanted. Maybe you can just delete rows from tables you're using as cache periodically at random using a scheduled job. Q: if there were an easy answer that exceeded your expectations based on Ignite 2, what would that behavior look like? On Mon, Jan 5, 2026 at 12:26 PM Pedro Rocha (Nokia) via user <[email protected]<mailto:[email protected]>> wrote: Hi, looking at the documentation, I can not find any references to eviction policy configuration - for any engine. Are these not configurable in ignite 3? We are using ignite strictly as a cache, using LRU (in ignite 2), and would like to use it also in ignite 3... Best regards, Pedro Rocha
