Bug 1479452

Summary:	Exposing routes based on a sharded router using NAMESPACE_LABELS takes too long.
Product:	OpenShift Container Platform	Reporter:	Jiří Mencák <jmencak>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	router	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	aos-bugs, pcameron, rchopra
Version:	3.6.0
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	aos-scalability-36
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-09 18:20:41 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 Jiří Mencák 2017-08-08 14:58:06 UTC

Description of problem:
Sharded routers based on project namespace labels take too long to register a route.  It can take around 7 minutes for the router to register a newly exposed route within a namespace.

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

How reproducible:
Always.


Steps to Reproduce:
https://asciinema.org/a/sMCJJ6ThrthFpQdVADG6Gy5YK

Actual results:
Routes take too long to register based on NAMESPACE_LABELS.

Expected results:
Near "immediate" registration of an exposed route on a NAMESPACE_LABELS-sharded router, just as it happens when using ROUTE_LABELS.

Additional info:
You can fast forward to end of the recording to see how long it can take for a route to become exposed.

Comment 1 Rajat Chopra 2017-08-08 17:59:03 UTC

Can you confirm that it is only when route is created on a newly created project?
On an existing project (one that has synced in ~10 minutes) the routes appear as quickly as in a non-sharded router. If yes, this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1355711

Comment 2 Jiří Mencák 2017-08-09 08:56:25 UTC

(In reply to Rajat Chopra from comment #1)
> Can you confirm that it is only when route is created on a newly created
> project?
Yes, this is correct.  Also, if I wait for the routes to be exposed correctly (those max ~10 minutes), I delete the project and re-create the project under the same name, the routes are exposed correctly immediately.  So this only seems to affect completely new namespaces for which routes have not been resynced with the router.  So, yes a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1355711.

Comment 3 Phil Cameron 2017-08-09 15:18:33 UTC

Also duplicate of: https://bugzilla.redhat.com/show_bug.cgi?id=1479295

Comment 4 Rajat Chopra 2017-08-09 18:20:41 UTC


*** This bug has been marked as a duplicate of bug 1479295 ***