Bug 1918675 - warnings and slowness for CLI operation after an update to ocp 4.6
Summary: warnings and slowness for CLI operation after an update to ocp 4.6
Keywords:
Status: CLOSED DUPLICATE of bug 1906332
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-21 10:56 UTC by mchebbi@redhat.com
Modified: 2024-03-25 17:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-21 11:46:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description mchebbi@redhat.com 2021-01-21 10:56:22 UTC
gathered information: https://cutt.ly/JjFYOy0

Customer is experiencing warnings and slowness for CLI operations since upgrading his cluster to 4.5 and then to 4.6.

[root@loutcvnd5804 ~]# oc get nodes
I0105 20:24:55.202503    9163 request.go:645] Throttling request took 1.11883936s, request: GET:https://console-openshift-console.apps.eng.openshift.tcc.etn.com:6443/apis/logging.openshift.io/v1?timeout=32s

oc get crd -o name | wc -l ==> 173 CRDs

I know that tere is several bugzilla raised about this issue and that those messages are triggered when the a number of CRD threshold is reached.

4.5:  create 100 CRDs in 100 groups, oc get on any of the CRDs gets throttling messages
4.7:  create 100 CRDs in 100 groups, oc get succeeds, no throttling
4.7:  create 200 CRDs in 200 groups, oc get on any of the CRDs gets throttling messages

------------------- 
200 seems like a low threshold for clusters with any sort of history.

is there a way to resolve those warnings and the slowness for CLI operations ?

Is there a way to identify CRDs that are no longer needed ?

Thanks for your help.

Comment 1 Maciej Szulik 2021-01-21 11:46:30 UTC
In 4.7 we've bumped the discovery burst to 250 see https://bugzilla.redhat.com/show_bug.cgi?id=1899575
It will be also backported to 4.6, see https://bugzilla.redhat.com/show_bug.cgi?id=1906332

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


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