Hi Val, I did further tests and it looks like OutOfMemoryError shows up in case the VM isn't fast enough with its GC. If you add e.g. cache.get in a loop for every key, it's possible to reproduce it. Doing System.gc() every thousand calls takes longer, but the VM has enough time for GC and it works. Nothing is referenced permanently, because a simple cache.get call is used. But I'm not sure how we can handle it in a high-load scenario. From my tests I can't see the coherency between size of Off-Heap-Memory and the required size of On-Heap-Memory to avoid a OutOfMemoryError.
Kind regards Peter 2016-06-29 11:00 GMT+02:00 Peter Schmitt <[email protected]>: > Hi Val, > > I've pushed a demo to https://github.com/ps4os/ignite_offheap_test > The issue is that I can't reproduce it consistently. As soon as I get the > OutOfMemoryError, I can reproduce it. And I can reproduce it with a restart > in between. > The demo contains a Readme as well as some TODOs and comments which > document the goals and observed issues. > > Kind regards > Peter > > > 2016-06-29 3:28 GMT+02:00 vkulichenko <[email protected]>: > >> Peter, >> >> This doesn't make much sense to me. With OFFHEAP_TIERED eviction policy >> should not change anything at all, so it sounds like misconfiguration. Can >> you provide the whole test that I can run and investigate? >> >> -Val >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Non-cluster-mode-tp5959p5982.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
