[NETVIRT-1384] Umbrella: Numerous new transaction leaks Created: 25/Jul/18  Updated: 31/Jul/18  Resolved: 31/Jul/18

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: Oxygen-SR2
Fix Version/s: Oxygen-SR3, Fluorine

Type: Bug Priority: Highest
Reporter: Michael Vorburger Assignee: Michael Vorburger
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File open-transactions-controller-0.txt     Text File open-transactions-controller-1.txt     Text File open-transactions-controller-2.txt    
Issue Links:
Blocks
is blocked by GENIUS-102 New OOM due to more TX leaks seen in ... Resolved
is blocked by GENIUS-178 Fix new transaction leaks in idmanager Resolved
is blocked by NETVIRT-1385 Transaction leak in NatInterfaceState... Resolved
is blocked by AAA-177 Suspected transaction leak in MDSALDy... Resolved
is blocked by NETVIRT-1291 New transaction leak in netvirt.fibma... Resolved
is blocked by NETVIRT-1379 Transaction leak in org.opendaylight.... Resolved
is blocked by NETVIRT-1380 Transaction leak in org.opendaylight.... Resolved
Relates
relates to GENIUS-176 Convert all of genius to managed tran... In Progress
Priority: Highest

 Description   

smalleni and SridharG have found numerous  new transaction leaks in internal scale testing, which we suspect could cause out of memory issues. We already chased a lot of those a while ago in NETVIRT-1010 (see also http://blog2.vorburger.ch/2017/09/how-to-find-transaction-related-memory.html), fixed everything we found - and now have a lot of new ones...

The attached x3 log files provide details. We will link (or sub-task) more specific issues; let us keep this issue (only) as the overall parent umbrella issue to link everything together to keep track.

 Comments   
Comment by Michael Vorburger [ 31/Jul/18 ]

Closing this, with Fix Version Fluorine and Oxygen SR3, as all linked issues are now (just) merged.

GENIUS-176 also needs to get done but "relates to" but doesn't "block" this issue.

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