karaf process killed by OS due to OOM condition (NETVIRT-974)

[NETVIRT-977] Track heap & native (!) memory usage logs Created: 03/Nov/17  Updated: 06/Nov/17

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Medium
Reporter: Michael Vorburger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by INTDIST-95 unable to add apache decanter repo in... Resolved
is blocked by INFRAUTILS-20 Monitorability of JVM's native memory... Resolved

 Description   

skitt and I had a discussion today how to best proceed on the parent issue, and AFTER the other two sub tasks have been clarified, would like to see more details about the evolution of both heap and native memory usage of this JVM in this scenario.

There are a couple of ways this could be obtained:

  1. using a JMX client such as VisualVM or Java Mission Control
  2. using Apache Karaf Decanter, need INTDIST-95
  3. using collectd, see e.g. Sai's blog ?
  4. using some custom ODL code that just logs - I'll try something in infrautils, see INFRAUTILS-19 and INFRAUTILS-20
Generated at Wed Feb 07 20:22:56 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.