If you’re using third-party persistence (or some other way to shift data into Ignite), you can use Expiry policies:
https://ignite.apache.org/docs/latest/configuring-caches/expiry-policies Using this, records that are not used in a given period of time can be removed. Eviction is based on space, expiry on time. Regards, Stephen > On 18 Jan 2021, at 16:13, Ryan Trollip <ryanonthebe...@gmail.com> wrote: > > Hey Stephen > > We have groups of data that used actively for a while, then not used for a > while, but may become active again later. > The intention here is to keep/cache active data in memory with ignite and to > somehow "archive" less active data to disk (free up its memory) based on a > policy, table, region or something, without going back and forth to a > separate database/warehouse implementation to off-load and on-load this data > from disk into the ignite cache. > > Thanks > Ryan > > > > On Mon, Jan 18, 2021 at 6:30 AM Stephen Darlington > <stephen.darling...@gridgain.com <mailto:stephen.darling...@gridgain.com>> > wrote: > What is your use case here? Why you need to evict data from memory on a > schedule rather than when it needs the memory? > > (The short version is that you can’t, but maybe if we understood what you’re > trying to do we can figure something out.) > > Regards, > Stephen > > > On 18 Jan 2021, at 11:46, Naveen <naveen.band...@gmail.com > > <mailto:naveen.band...@gmail.com>> wrote: > > > > Hi > > > > Apart from LRU, we dont have any other eviction policy. > > If we want to flush or evict a record with a ttl , we need to build a new > > eviction policy right ? > > OR any other ways of achieving this > > > > Thanks > > Naveen > > > > > > > > -- > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > <http://apache-ignite-users.70518.x6.nabble.com/> > >
