Bug 2080925 - Dont spawn go routines when adding metric event
Summary: Dont spawn go routines when adding metric event
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10-rc3
Hardware: All
OS: All
Target Milestone: ---
: 4.10.z
Assignee: Martin Kennelly
QA Contact: Anurag saxena
Depends On: 2080924
TreeView+ depends on / blocked
Reported: 2022-05-02 11:33 UTC by Martin Kennelly
Modified: 2022-05-18 11:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2080924
Last Closed: 2022-05-18 11:51:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 1071 0 None open WIP: Bug 2080925: Don't spawn go routines for adding metric events 2022-05-02 11:34:30 UTC
Red Hat Product Errata RHBA-2022:2178 0 None None None 2022-05-18 11:51:13 UTC

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.


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