What's your -Xmx for your JVM set to, and how much memory does your droplet have? Does it have any swap space? My guess is you need to reduce the heap size of your JVM and the OS is killing your process because there is not enough memory left.
-Dan On Fri, Apr 22, 2016 at 1:55 PM, Darrel Schneider <[email protected]> wrote: > I don't know why your OS would be killing your process which seems like your > main problem. > > But I did want you to know that if you don't have any regions with > off-heap=true then you have no reason to have off-heap-memory-size to be set > to anything other than 0. > > On Fri, Apr 22, 2016 at 12:48 PM, Eugene Strokin <[email protected]> > wrote: >> >> I'm running load tests on the Geode cluster I've built. >> The OS is killing my process occasionally, complaining that the process >> takes too much memory: >> >> # dmesg >> [ 2544.932226] Out of memory: Kill process 5382 (java) score 780 or >> sacrifice child >> [ 2544.933591] Killed process 5382 (java) total-vm:3102804kB, >> anon-rss:335780kB, file-rss:0kB >> >> Java doesn't have any problems, I don't see OOM exception. >> Looks like Geode is using off-heap memory. But I set offHeap to false for >> my region, and I do have only one region: >> >> RegionFactory<String, byte[]> regionFactory = cache.createRegionFactory(); >> regionFactory >> .setDiskStoreName("-ccio-store") >> .setDataPolicy(DataPolicy.PERSISTENT_PARTITION) >> .setOffHeap(false) >> .setCacheLoader(new AwsS3CacheLoader()); >> >> Also, I've played with off-heap-memory-size setting, setting it to small >> number like 20M to prevent Geode to take too much off-heap memory, but >> result is the same. >> >> Do you have any other ideas what could I do here? I'm stack at this point. >> >> Thank you, >> Eugene > >
