Unsubscribe
Sent from Mail for Windows 10
Re: Ignite DataStreamer Memory Problems
No luck with the changed configuration. Memory still continues to rise until the Kubernetes limit (110GB), then crashes. This is output I pulled from jcmd at some point before the crash. I can post the detailed memory report if that helps. Total: reserved=84645150KB, committed=83359362KB - Java Heap (reserved=25165824KB, committed=25165824KB) (mmap: reserved=25165824KB, committed=25165824KB) - Class (reserved=1121992KB, committed=80356KB) (classes #11821) (malloc=1736KB #20912) (mmap: reserved=1120256KB, committed=78620KB) -Thread (reserved=198099KB, committed=198099KB) (thread #193) (stack: reserved=197248KB, committed=197248KB) (malloc=626KB #975) (arena=225KB #380) - Code (reserved=260571KB, committed=65571KB) (malloc=10971KB #16284) (mmap: reserved=249600KB, committed=54600KB) -GC (reserved=1047369KB, committed=1047369KB) (malloc=80713KB #57810) (mmap: reserved=966656KB, committed=966656KB) - Compiler (reserved=597KB, committed=597KB) (malloc=467KB #1235) (arena=131KB #7) - Internal (reserved=56763248KB, committed=56763248KB) (malloc=56763216KB #1063361) (mmap: reserved=32KB, committed=32KB) -Symbol (reserved=17245KB, committed=17245KB) (malloc=14680KB #138104) (arena=2565KB #1) -Native Memory Tracking (reserved=20852KB, committed=20852KB) (malloc=453KB #6407) (tracking overhead=20399KB) - Arena Chunk (reserved=201KB, committed=201KB) (malloc=201KB) - Unknown (reserved=49152KB, committed=0KB) (mmap: reserved=49152KB, committed=0KB) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Ignite DataStreamer Memory Problems
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 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 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/ >> >
Re: Ignite DataStreamer Memory Problems
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 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/ >
Re: Ignite DataStreamer Memory Problems
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/
