I suspect you might hit it again if you run it a bit longer because of this
[Thu Nov 2 05:58:08 2017] Free swap = 0kB [Thu Nov 2 05:58:08 2017] Total swap = 0kB On Thu, Nov 9, 2017 at 1:39 AM, Stephen Kitt <[email protected]> wrote: > On Thu, 9 Nov 2017 10:28:14 +0100 > Robert Varga <[email protected]> wrote: > > On 02/11/17 23:02, Luis Gomez wrote: > > > 1) JVM does not kill itself, the OS does instead after the java > > > process grows to 3.7G in a VM of 4G RAM (note Xmx is set to 2G but > > > still the jvm goes far beyond that). > > > > Indicates this lies out side of heap -- check thread count. > > We verified separately that this is an OOM issue, but one detected by > the kernel rather than by the JVM (the OOM killer kills the JVM, see > https://jira.opendaylight.org/secure/attachment/14207/dmesg.log.txt > for details; the number of threads wasn’t an issue here, but the lack > of swap probably didn’t help). > > Upgrading to OpenJDK 8 patch 151 fixed the problem, it might have been > related to one of the several memory usage bugs in 144 that were fixed > in 151. It’s probably just moving the goalposts though since the > problem was new — basically, I suspect we recently started using a > little too much off-heap memory for some reason, and the upgrade to 151 > reduces the JVM’s memory usage enough to make us fit in our VMs again. > > Regards, > > Stephen > > _______________________________________________ > controller-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/controller-dev > > -- Thanks Anil
_______________________________________________ controller-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/controller-dev
