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