Bug 1812004
Summary: | Node CPU stats are not accurate in Openshift 4.3 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Dan McGinnes <MCGINNES> |
Component: | Monitoring | Assignee: | Pawel Krupa <pkrupa> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.z | CC: | alegrand, anpicker, erooth, kakkoyun, lcosic, mdhanve, mloibl, pkrupa, surbania, syangsao |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: usage of rate() was smoothing statistics data
Consequence: spikes in CPU usage weren't represented
Fix: rate() was changed to irate()
Result: spikes are shown and `oc adm top` UX is similar to linux `top` utility
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:19:21 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
Dan McGinnes
2020-03-10 11:26:05 UTC
Tested with 4.5.0-0.nightly-2020-03-25-200754, check on one node, there is not much difference for cpu usage for the following two quries 100 - (avg by (instance) (irate(node_cpu_seconds_total{mode="idle",instance="ip-10-0-152-12.ap-northeast-2.compute.internal"}[10m])) * 100) Element Value {instance="ip-10-0-152-12.ap-northeast-2.compute.internal"} 23.26666666667127 # kubectl top node ip-10-0-152-12.ap-northeast-2.compute.internal NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% ip-10-0-152-12.ap-northeast-2.compute.internal 899m 25% 4253Mi 29% *** Bug 1816500 has been marked as a duplicate of this bug. *** *** Bug 1850270 has been marked as a duplicate of this bug. *** 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/RHBA-2020:2409 |