On 11/03/2017 10:24 AM, Michael Vorburger wrote: > On Fri, Nov 3, 2017 at 11:02 AM, Stephen Kitt <[email protected] > <mailto:[email protected]>> wrote: > > On Fri, 3 Nov 2017 10:56:48 +0100 > Stephen Kitt <[email protected] <mailto:[email protected]>> wrote: > > Another avenue could be to look at the overcommit settings, but I > > suspect that the JVM would fail to start altogether if we adjusted > > those. > > Actually that’s worth trying anyway: > > sysctl -w vm.overcommit_memory=2 > > before starting the JVM, will prevent it from over-allocating memory. > We’ll get a heap dump when that happens, if the JVM actually manages to > start (which I suspect it won’t, with a 2G Xmx on a 4G system). > > > > https://jira.opendaylight.org/browse/NETVIRT-974 now has some sub-tasks for > various next actions..
I've updated NETVIRT-975 [0]. The TL;DR is that with a different host image we do not see the crash. I'm looking for opinions on the next steps, one of which could be that we update our images, close the bug and forget this ever happened :) JamO [0] https://jira.opendaylight.org/browse/NETVIRT-974?focusedCommentId=59941&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-59941 _______________________________________________ controller-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/controller-dev
