Bug 2088449 - network-metrics-daemon makes costly global pod list calls scaling per node
Summary: network-metrics-daemon makes costly global pod list calls scaling per node
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.8.z
Assignee: Sebastian Scheinkman
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On: 2087049
Blocks: 2064371
TreeView+ depends on / blocked
 
Reported: 2022-05-19 13:13 UTC by OpenShift BugZilla Robot
Modified: 2022-06-01 21:18 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-01 21:18:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift network-metrics-daemon pull 52 0 None open [release-4.8] Bug 2088449: Fix field selector 2022-05-24 01:00:55 UTC
Red Hat Product Errata RHBA-2022:4737 0 None None None 2022-06-01 21:18:13 UTC

Comment 3 Weibin Liang 2022-05-26 19:34:48 UTC
Scale a cluster with 18187 pods, did't see large range reads on pods in 4.8.0-0.nightly-2022-05-26-082821


[weliang@weliang ~]$ oc logs etcd-ip-10-0-196-2.us-east-2.compute.internal | grep range_response_count
error: a container name must be specified for pod etcd-ip-10-0-196-2.us-east-2.compute.internal, choose one of: [etcdctl etcd etcd-metrics etcd-health-monitor] or one of the init containers: [setup etcd-ensure-env-vars etcd-resources-copy]
[weliang@weliang ~]$ oc logs etcd-ip-10-0-196-2.us-east-2.compute.internal -c etcd | grep range_response_count
{"level":"warn","ts":"2022-05-26T19:22:55.030Z","caller":"etcdserver/util.go:163","msg":"apply request took too long","took":"127.981229ms","expected-duration":"100ms","prefix":"read-only range ","request":"key:\"/kubernetes.io/namespaces/e03f8864-3a62-40de-8f74-8ff16286539f\" ","response":"range_response_count:1 size:1007"}
{"level":"warn","ts":"2022-05-26T19:22:55.030Z","caller":"etcdserver/util.go:163","msg":"apply request took too long","took":"123.276821ms","expected-duration":"100ms","prefix":"read-only range ","request":"key:\"/kubernetes.io/serviceaccounts/openshift-kube-controller-manager/localhost-recovery-client\" ","response":"range_response_count:1 size:424"}
{"level":"warn","ts":"2022-05-26T19:22:55.031Z","caller":"etcdserver/util.go:163","msg":"apply request took too long","took":"114.272541ms","expected-duration":"100ms","prefix":"read-only range ","request":"key:\"/kubernetes.io/pods/e03f8864-3a62-40de-8f74-8ff16286539f/node-density-10564\" ","response":"range_response_count:1 size:3528"}
{"level":"warn","ts":"2022-05-26T19:22:55.031Z","caller":"etcdserver/util.go:163","msg":"apply request took too long","took":"122.457013ms","expected-duration":"100ms","prefix":"read-only range ","request":"key:\"/kubernetes.io/pods/e03f8864-3a62-40de-8f74-8ff16286539f/node-density-10565\" ","response":"range_response_count:1 size:3528"}
{"level":"warn","ts":"2022-05-26T19:28:07.872Z","caller":"etcdserver/util.go:163","msg":"apply request took too long","took":"107.118251ms","expected-duration":"100ms","prefix":"read-only range ","request":"key:\"/kubernetes.io/pods/e03f8864-3a62-40de-8f74-8ff16286539f/\" range_end:\"/kubernetes.io/pods/e03f8864-3a62-40de-8f74-8ff16286539f0\" ","response":"range_response_count:16806 size:60876093"}
[weliang@weliang ~]$ oc get pod --all-namespaces | wc -l
18187
[weliang@weliang ~]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2022-05-26-082821   True        False         70m     Cluster version is 4.8.0-0.nightly-2022-05-26-082821
[weliang@weliang ~]$

Comment 5 errata-xmlrpc 2022-06-01 21:18:03 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 (OpenShift Container Platform 4.8.42 bug fix update), 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/RHBA-2022:4737


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