[TSDR-29] heap dump after OutOfMemoryError when loading cassandra feature with all integration compatible features. Created: 31/Aug/16  Updated: 22/Mar/18  Resolved: 22/Mar/18

Status: Resolved
Project: tsdr
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Jamo Luhrsen Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Zip Archive java_pid30927_Leak_Suspects.zip    
External issue ID: 6602

 Description   

steps to reproduce:

opendaylight-user@root>repo-add mvn:org.opendaylight.integration/features-integration-test/0.5.0-SNAPSHOT/xml/features
Adding feature url mvn:org.opendaylight.integration/features-integration-test/0.5.0-SNAPSHOT/xml/features
opendaylight-user@root>feature:install odl-integration-compatible-with-all
Refreshing bundles org.apache.sshd.core (30)
opendaylight-user@root>feature:install odl-restconf
opendaylight-user@root>feature:install odl-tsdr-cassandra
opendaylight-user@root>feature:install odl-tsdr-openflow-statistics-collector
java.lang.OutOfMemoryError: GC overhead limit exceeded
Dumping heap to java_pid30927.hprof ...
Heap dump file created [2872209701 bytes in 19.614 secs]

email discussion:

https://lists.opendaylight.org/pipermail/tsdr-dev/2016-August/000966.html

 Comments   
Comment by Jamo Luhrsen [ 01/Sep/16 ]

Attachment java_pid30927_Leak_Suspects.zip has been added with description: leak suspects report from MAT

Comment by A H [ 02/Sep/16 ]

Is there an ETA for this bug and someone assigned to fix?

Comment by yuling chen [ 02/Sep/16 ]

Hi An,

This bug is not going to be fixed in Boron release considering it is not a blocker.

The target of the fix is SR1.

Thanks,
YuLing

Comment by Jamo Luhrsen [ 02/Sep/16 ]

(In reply to yuling chen from comment #3)
> Hi An,
>
> This bug is not going to be fixed in Boron release considering it is not a
> blocker.
>
> The target of the fix is SR1.
>
> Thanks,
> YuLing

I think normally an easy to hit OOM crash should be a blocker though. Why
not this one?

Comment by Tom Pantelis [ 22/Mar/18 ]

The leak suspect reports indicates org.opendaylight.controller.md.sal.dom.xsql.XSQLBluePrint as the culprit. That bundle was known to leak/retain memory and has since been removed.

Generated at Wed Feb 07 20:46:11 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.