Bug 1473042 - [3.6] ResourceQuota controller observed making excessive LIST calls at scale
[3.6] ResourceQuota controller observed making excessive LIST calls at scale
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Kubernetes (Show other bugs)
3.6.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Derek Carr
Zhang Cheng
:
Depends On:
Blocks: 1473370
  Show dependency treegraph
 
Reported: 2017-07-19 19:30 EDT by Derek Carr
Modified: 2017-08-16 15 EDT (History)
5 users (show)

See Also:
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 01:31:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/origin/pull/15357 None None None 2017-07-20 14:28 EDT

  None (edit)
Description Derek Carr 2017-07-19 19:30:49 EDT
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 01:31:01 EDT
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

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