I've put a full answer on SO - https://stackoverflow.com/questions/55752357/possible-memory-leak-in-ignite-datastreamer/55786023#55786023 .
In short, so far it doesn't look like a memory leak to me - just a misconfiguration. There is a memory pool in JVM for direct memory buffers which is by default bounded by the value of `-Xmx`. Most applications would use minuscule amount of it, but in some it can grow - and grow to the size of the heap, making your total Java usage not roughly `heap + data region` but `heap * 2 + data region`. Set walSegmentSize=64mb and -XX:MaxDirectMemorySize=256mb and I think it's going to be OK. Stan On Sun, Apr 21, 2019 at 11:51 AM Denis Magda <dma...@apache.org> wrote: > Hello, > > Copying Evgeniy and Stan, our community experts who'd guide you through. > In the meantime, please try to capture the OOM with this approach: > > https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/tooldescr007.html > > - > Denis > > > On Sun, Apr 21, 2019 at 8:49 AM kellan <kellan.bur...@gmail.com> wrote: > >> Update: I've been able to confirm a couple more details: >> >> 1. I'm experiencing the same leak with put, putAll as I am with the >> DataStreamer >> 2. The problem is resolved when persistence is turned off >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
