Bug 2080925

Summary:	Dont spawn go routines when adding metric event
Product:	OpenShift Container Platform	Reporter:	Martin Kennelly <mkennell>
Component:	Networking	Assignee:	Martin Kennelly <mkennell>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	anusaxen
Version:	4.10-rc3
Target Milestone:	---
Target Release:	4.10.z
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2080924	Environment:
Last Closed:	2022-05-18 11:51:02 UTC	Type:	---
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:	2080924
Bug Blocks:

Description Martin Kennelly 2022-05-02 11:33:39 UTC

+++ This bug was initially created as a clone of Bug #2080924 +++

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 6 errata-xmlrpc 2022-05-18 11:51:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.10.14 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2178