Bug 1473042

Summary: [3.6] ResourceQuota controller observed making excessive LIST calls at scale
Product: OpenShift Container Platform Reporter: Derek Carr <decarr>
Component: NodeAssignee: Derek Carr <decarr>
Status: CLOSED ERRATA QA Contact: Zhang Cheng <chezhang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: aos-bugs, eparis, jokerman, mmccomas, smunilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1473370 (view as bug list) Environment:
Last Closed: 2017-08-10 05:31:01 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: 1473370    

Description Derek Carr 2017-07-19 23:30:49 UTC
Description of problem:
For all resources other than Pod or PersistentVolumeClaim, the quota controller is making a LIST call per namespace to determine current usage counts.  This can cause quota recalculation to take an extended period of time.  Secret, ConfigMap, ReplicationControllers, Services, and ResourceQuota quota items should have usage reconciled via a shared informer.

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


How reproducible:
always

Steps to Reproduce:
1. oc create quota quota --hard=services=10,secrets=10
2.
3.

Actual results:
quota controller should not make LIST calls per namespace when doing recalculation.

Expected results:
quota controller calculates usage from shared informer.

Additional info:
none

Comment 7 errata-xmlrpc 2017-08-10 05:31:01 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/RHEA-2017:1716