Bug 1720653

Summary:	measure the time needed by ovn-controller to resync to a new SB db
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	lorenzo bianconi <lorenzo.bianconi>
Component:	openvswitch2.12	Assignee:	lorenzo bianconi <lorenzo.bianconi>
Status:	CLOSED ERRATA	QA Contact:	ying xu <yinxu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	RHEL 7.7	CC:	ctrautma, jhsiao, jishi, kfida, ralongi, tredaelli
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openvswitch2.12-2.12.0-9.el7fdn	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1776883 1780719 (view as bug list)		Environment:
Last Closed:	2020-01-21 16:04:54 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:	1776883

Description lorenzo bianconi 2019-06-14 13:08:29 UTC

Additional info:
We are interested in the time that it takes ovn-controller to resync to a
different southbound database with substantially the same content.

So for example after creating a lot of logical switches and switch
ports like in the scale tests, copy the southbound database file (or
create an entirely new one with different switches and ports) and start
a new ovsdb-server on a different port on the server.  The change ovn-
remote in the local vswitch and see how long it takes for ovn-
controller to update the flows in OVS based on the new database.

Girish said that the buffers that ovn-controller used to download the
new database were pretty small and when they bumped the size from IIRC
4k -> 64k the download itself went quite a bit faster.

But in the end, it is not clear what the delay from (a) change ovn-
remote to (b) OVS flows are synchronized, is and if we need to look
into optimizing that.

Comment 2 Jianlin Shi 2019-12-11 02:39:32 UTC

Hi lorenzo,

could you tell us how could we test the bug?

Thanks & Best Regards,
Jianlin Shi

Comment 3 ying xu 2020-01-13 08:38:46 UTC

test on version 2.12-8
start time:
Mon Jan 13 03:32:00 EST 2020
end time:
Mon Jan 13 03:33:41 EST 2020

time=1:41

test on version 2.12-12
start time:
Mon Jan 13 03:07:04 EST 2020
end time:
Mon Jan 13 03:08:12 EST 2020

time=1:08

set verified

Comment 5 errata-xmlrpc 2020-01-21 16:04:54 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, 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-2020:0168