Re: Using more memory than is physically available
Hello! If you want to store more data on node than available Data Regions memory, your course of action should be Ignite Native Persistence. You can also use Expiry if the data is not crucial and you want to put limit on amount of data. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Using more memory than is physically available
I can afford to lose data. My ignite cache is embedded within an application running in open shift (docker containers) and has setClientMode(false). All data stored in docker containers is lost on pod restarts. Which would be preferable? Using ignite persistence or swap space? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Using more memory than is physically available
If you don't want to lose the data, which doesn't fit in RAM, on restarts then go for Ignite persistence. If it's fine to lose the data on restarts then the OS swapping is a good option as well: https://apacheignite.readme.io/docs/swap-space -- Denis On Thu, Aug 9, 2018 at 2:33 PM nitin.phad...@optum.com < nitin.phad...@optum.com> wrote: > Will Apache Ignite allow me to use more memory than is physically available > on my system? > > If yes, Do I need to turn persistence on? > > If I do not need to turn persistence on , how do I specify the location on > disk to which memory will be swapped? > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Using more memory than is physically available
Will Apache Ignite allow me to use more memory than is physically available on my system? If yes, Do I need to turn persistence on? If I do not need to turn persistence on , how do I specify the location on disk to which memory will be swapped? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
