Bug 2004299 - virt-handler goroutine count increases over time
Summary: virt-handler goroutine count increases over time
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 4.8.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.12.0
Assignee: Itamar Holder
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
: 2004295 2004300 (view as bug list)
Depends On: 2004295 2004300
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-14 23:43 UTC by Sarah Bennert
Modified: 2023-01-26 13:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2004295
Environment:
Last Closed: 2022-10-12 11:02:05 UTC
Target Upstream Version:
Embargoed:
sbennert: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1996660 1 high CLOSED [4.8] Goroutine count and memory remains high after VMIs are removed 2023-01-26 13:10:52 UTC
Red Hat Issue Tracker CNV-14275 0 None None None 2023-01-26 13:01:57 UTC

Description Sarah Bennert 2021-09-14 23:43:52 UTC
+++ This bug was initially created as a clone of Bug #2004295 +++

Tracking for 4.9.z

Description of problem:
  Opened as a follow-up to https://bugzilla.redhat.com/show_bug.cgi?id=1996660
  Observed an additional slower goroutine leak.

How reproduceible:
  Very reproduceible, must be run for an extended time to observe increase.

Steps to Reproduce:
  Allow for any stabilization between each step.
  While observing goroutines metric on virt-handler,
    1. Create and Start a batch of 100-300 VMs
    2. Delete all VMs in batch
    3. Repeat

Expected Results:
  Goroutines do not increase between VM deployments after initial deployment

Actual Results:
  Over the course of approximately 48 hours, goroutine count increased between 14-28 per virt-handler.

Comment 2 Geetika Kapoor 2022-06-08 11:54:10 UTC
*** Bug 2004295 has been marked as a duplicate of this bug. ***

Comment 3 Geetika Kapoor 2022-06-08 11:54:47 UTC
*** Bug 2004300 has been marked as a duplicate of this bug. ***

Comment 4 sgott 2022-08-03 15:24:04 UTC
removing the target version to cause us to re-triage this -- to see if it still applies.

Comment 5 sgott 2022-08-10 12:26:04 UTC
Kedar, does this sitll manifest with current releases?

Comment 6 Kedar Bidarkar 2022-09-07 12:35:03 UTC
Sarah, Do we still see this issue with latest 4.11.0 ?

Comment 7 Itamar Holder 2022-10-12 11:00:51 UTC
I confirm that this behavior no longer occurs on 4.11 clusters.


Note You need to log in before you can comment on or make changes to this bug.