Val, That’s no longer works for 2.0.
You need to define a memory region with specific maximum size [1]. However, the data will not be swapped to disk once the max threshold is reached. To support a use case you have you need to wait for the Ignite Distributed Persistent store to be released or use a 3rd party database and enable a page eviction policy for the region [2]. [1] https://apacheignite.readme.io/docs/page-memory#memory-policies <https://apacheignite.readme.io/docs/page-memory#memory-policies> [2] https://apacheignite.readme.io/docs/evictions#section-page-based-eviction — Denis > On Jun 8, 2017, at 4:24 PM, vkulichenko <[email protected]> wrote: > > For on-heap memory you can use eviction policies: > https://apacheignite.readme.io/docs/evictions > For off-heap limit is specified in CacheConfiguration#offHeapMaxMemory > property. > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Swapping-to-Disk-Ignite-2-0-tp13522p13538.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
