> It looks like documentation is misleading. I partially agree. CacheConfiguration is validated during creation of a cache (when you call a ignite.getOrCreateCache) and some mismatches like OFFHEAP mode with offHeapMaxMemory equlas -1 will be resolved.
Maybe it makes sense to add explanation to 'offHeapMaxMemory' field in Ignite 1.9. As far as I know Ignite-2.0 is moving to full-off-heap page memory model, and CacheConfiguration will be remade, including the removal of 'offHeapMaxMemory' field. 2017-04-27 2:39 GMT+03:00 javastuff....@gmail.com <javastuff....@gmail.com>: > It looks like documentation is misleading. > > Tried test program - > > - without setting offHeapMaxMemory, getOffHeapMaxMemory returns 0. > - Setting offHeapMaxMemory=-1, getOffHeapMaxMemory returns 0. > > Thanks, > -Sam > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Offheap-and-max-memory-tp12275p12277.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best Regards, Vyacheslav
