Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1973447

Summary:	ovn-dbchecker peak memory spikes to ~500MiB during cluster-density run
Product:	OpenShift Container Platform	Reporter:	Mohit Sheth <msheth>
Component:	Networking	Assignee:	Tim Rozet <trozet>
Networking sub component:	ovn-kubernetes	QA Contact:	Mike Fiedler <mifiedle>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	bbennett, msheth, zzhao
Version:	4.8
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	perfscale-ovn
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:04:21 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:

Description Mohit Sheth 2021-06-17 20:19:38 UTC

Description of problem:
When I run cluster-density with 500 namespaces on a cluster with 20 nodes, sharp peaks are observed multiple (~10) times which show that the ovn-dbchecker container consumes ~500MiB RSS. 

Version-Release number of selected component (if applicable):
4.8.0-0.nightly-2021-06-13-101614

How reproducible:
Always

Steps to Reproduce:
1. Run cluster-density on 20 nodes with 500 namespaces

Actual results:
Sharp peaks for ovn-dbchecker

Expected results:
No sharp peaks

Additional info:

Comment 4 Tim Rozet 2021-10-06 18:32:53 UTC

root cause is ovsdb-tool loading the entire database and consuming a lot of CPU to search for the server id. https://bugzilla.redhat.com/show_bug.cgi?id=2011468 is filed to track this on the OVSDB side

Comment 5 Tim Rozet 2021-10-08 19:20:42 UTC

removing the dependent ovsdb-tool bug. We will migrate to using ovn-appctl in ovn-kubernetes:
https://github.com/ovn-org/ovn-kubernetes/pull/2554

Comment 7 Mike Fiedler 2021-12-03 20:41:31 UTC

Verified on 4.10.0-0.nightly-2021-12-02-140313.  20 node cluster and 500 iteration cluster-density.   No spikes in ovn-dbchecker memory usage - it was stable at 22-26 MiB throughout the run.

Comment 12 errata-xmlrpc 2022-03-10 16:04:21 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056