Bug 1600871
| Summary: | Pod memory discrepancies between web console and cmdline | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sudarshan Chaudhari <suchaudh> | ||||
| Component: | Hawkular | Assignee: | Ruben Vargas Palma <rvargasp> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Junqi Zhao <juzhao> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.0 | CC: | aos-bugs, ktadimar, suchaudh | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.6.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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: | |||||||
| Attachments: |
|
||||||
Hello, Is there any update on this? Thanks. I was out all last week and just saw this ticket for the first time yesterday. The console queries Hawkular Metrics for the values which are aggregated to provide a fixed number of data points for a given time range, e.g., 60 data points over the past two hours. The raw data is collected from cAdvisor on each node by Heapster and then sent to Hawkular Metrics for persistence. I am not sure how `oc adm top pod` works, but I do know that it does *not* fetch values from Hawkular Metrics. It could be displaying raw values. I am not at all surprised that there is some discrepancy. OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift |
Created attachment 1458686 [details] Memory Metrics of the pod Description of problem: When checking the memory utilization of pods, the memory consumption in Openshift Console Metrics differs from the command line after checking using the command: `oc adm top pod` For the pod: [root@master01 ~]# oc get pods NAME READY STATUS RESTARTS AGE httpd-1-qv7mx 1/1 Running 0 9d From Openshift Console: Memory is: 15.9Mi Check the attached SNAP(Memory usage). From the Command Line: [root@master01 ~]# oc adm top pods NAME CPU(cores) MEMORY(bytes) httpd-1-qv7mx 2m 10Mi In other test, the difference was lot: From Openshift Console: Memory of pod: 2047Mi From Command Line: Memory of Pod: 1795Mi [elijah_eng@master01 ~]$ oc adm top pod NAME CPU(cores) MEMORY(bytes) pr-v2-8-k3rwb 13m 1799Mi pr-v2-8-nsv6k 19m 1793Mi pr-v2-8-cffvv 9m 1800Mi pr-v2-8-fjp4v 14m 1795Mi How reproducible: Always. I have reproduced on OCP 3.6 and 3.9 Steps to Reproduce: 1. Check the metrics on Openshift console > Pods 2. run the command # oc adm top pod Actual results: The Memory usage is different Expected results: The metrics should be the same in GUI as well as CLI Additional info: Need justification/fix on this.