Shawn, good to hear this, Just in case here is you can find some tips and tricks on memory and garbage collection tuning for Ignite: https://apacheignite.readme.io/docs/durable-memory-tuning https://apacheignite.readme.io/docs/jvm-and-system-tuning
— Denis > On Dec 12, 2017, at 10:50 PM, shawn.du <[email protected]> wrote: > > Thank you Denis, > > I think OOM is caused by invalid configuration. for I supposed ignite use > on-heap memory, I set a very big value for > -Xmx -Xms, in this way, memory left for off-heap and other programs is > limited. > We are run testing now, till now all seems good. > > Thanks > Shawn > > On 12/13/2017 07:36，Denis Magda<[email protected]> <mailto:[email protected]> > wrote： > Shawn, > > If you still need to use the on-heap caching by some reason make sure you > enabled an eviction policy: > https://apacheignite.readme.io/docs/evictions#section-java-heap-cache > <https://apacheignite.readme.io/docs/evictions#section-java-heap-cache> > > Otherwise the on-heap cache will grow endlessly. > > BTW, what kind of OOM you got? It might be off-heap or on-heap caching > related. Share the whole stack trace. > > — > Denis > >> On Dec 12, 2017, at 4:37 AM, slava.koptilin <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Shawn, >> >>> how to disable off heap completely? >> You cannot disable off-heap. As of 2.0, Apache Ignite stores all the data >> outside of java heap. >> >>> does it mean half in on-heap and half in off-heap? >> On-heap caching allows to get a subset of the data into java heap >> and can be useful for scenarios when you do a lot of cache reads on server >> nodes that work with cache entries in the binary form >> or invoke cache entry deserialization. >> >> Thanks! >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> <http://apache-ignite-users.70518.x6.nabble.com/> > >
