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]> 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 >
