karaf process killed by OS due to OOM condition
(NETVIRT-974)
|
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Jamo Luhrsen |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
https://lists.opendaylight.org/pipermail/controller-dev/2017-November/014037.html add the following magic incantations to the JVM options, DEFAULT_JAVA_OPTS="$DEFAULT_JAVA_OPTS -XX:+HeapDumpOnOutOfMemoryError -XX:NativeMemoryTracking=detail -XX:+UnlockDiagnosticVMOptions -XX:+PrintNMTStatistics -XX:-AutoShutdownNMT" BUT the Kernel OOM killer will do SIGKILL (kill -9) so AutoShutdownNMT most likely won't work, but if we could obtain native memory usage during normal runtime via the following command, if you manage to run that some time (shortly) before it dies, that would still be interesting to see: jcmd <PID> VM.native_memory detail scale=MB |