Bug 1380673

Summary: 404 in Openshift Logs on nodes
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: HawkularAssignee: Matt Wringe <mwringe>
Status: CLOSED WONTFIX QA Contact: Peng Li <penli>
Severity: low Docs Contact:
Priority: medium    
Version: 3.2.1CC: aos-bugs
Target Milestone: ---   
Target Release: ---   
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: 2017-02-09 20:28:49 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:

Description Miheer Salunke 2016-09-30 10:03:42 UTC 
Description of problem:

I see the following logs on node. It is apparently related to Heapster?
Is this normal or what is wrong? Logs added in private comment due to confidential reasons.

Is it normal I get so many 404 call from heapster in node logs? It effectively seems to be old build.... Therefor obviously probably not running anymore... Is this the reason?

In sysconfig I still have the default logging:
OPTIONS=--loglevel=2

It did not changed....

For heapster also they are using the default logging.

If I correctly understand it get metrics for all pod of the cluster on each node? Or you mean something else?
Because if there is 100 nodes, it is highly inefficient.....

Version-Release number of selected component (if applicable):
3.2.0

How reproducible:
Always

Steps to Reproduce:
1. Mentioned in the description
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Matt Wringe 2016-09-30 16:29:35 UTC 
I am not sure if its the right approach to increase the logging levels, view some info level messages and automatically assume that its functioning in an inefficient manner.

I have not looked more closely into this issue, so I don't even know if this is actually inefficient or if its actually handling things in a correct manner.

I could consider that what it is doing is asking OpenShift for the list of pods, OpenShift is then returning the list and Heapster is trying to access the metrics for this list of pods.

It may be more efficient to just try and gather the metrics directly instead of requesting more information about whether or not the pods is currently running and then trying to gather the metrics for the pod if it is.

But it does look like it something which Heapster maybe could handle a bit better. This could could also be fixed in a newer version of Heapster.

If this was filling up the customers logs by default with these types of messages, then yes, this would be considered a bug and something which we would look into and fix.

For now, this shouldn't be considered a high priority unless its actually causing problems for users.
Comment 3 Matt Wringe 2017-02-09 20:28:49 UTC 
Heapster is being deprecated and I don't believe it is worth the effort looking more deeply into this issue at this particular point in time.