Bug 2080924

Summary: Dont spawn go routines when adding metric event
Product: OpenShift Container Platform Reporter: Martin Kennelly <mkennell>
Component: NetworkingAssignee: Martin Kennelly <mkennell>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED WONTFIX Docs Contact:
Severity: medium    
Priority: medium    
Version: 4.11   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2080925 (view as bug list) Environment:
Last Closed: 2024-04-30 18:04:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2080925    

Description Martin Kennelly 2022-05-02 11:31:56 UTC 
Description of problem:
Adding a goroutine for each event either from libovsdb cache or from ovnkube-master informer handler may cause golang needless pressure for go runtime to spawn so many go routines.

Version-Release number of selected component (if applicable):


How reproducible:
Unknown. Youd have to create a large amount of events. It was seen once during runtime that libovsdb cache was dropping events and we suspect it was due to the metrics handler. We could not prove for sure that this was the case however.

Steps to Reproduce:
1. Create a very large amount of events from OVN
2. Libovsdb cache will log that it is dropping events due to queue full


Actual results:


Expected results:


Additional info:
Comment 1 Rory Thrasher 2024-04-30 18:04:53 UTC 
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary