Bug 1387269 - Metrics not available error after sitting idle at metrics tab for several minutes
Summary: Metrics not available error after sitting idle at metrics tab for several min...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Matt Wringe
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 13:53 UTC by Justin Pierce
Modified: 2016-10-31 17:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-31 16:13:19 UTC
Target Upstream Version:


Attachments (Terms of Use)
Error message (143.39 KB, image/png)
2016-10-20 13:53 UTC, Justin Pierce
no flags Details

Description Justin Pierce 2016-10-20 13:53:43 UTC
Created attachment 1212523 [details]
Error message

Description of problem:
If you sit idle at the pod metrics tab for about 10 minutes, an error is displayed by the console. Reloading the page fixes this problem.

Version-Release number of selected component (if applicable):
3.3
Firefox 47

How reproducible:
100%

Steps to Reproduce:
1. Instantiate a pod
2. Navigate to the pod metrics tab
3. Do nothing for 10 minutes

Actual results:
The metrics are eventually replaced with an error.

Expected results:
Availability of the metrics should correspond to the web console session length. 

Additional info:

Comment 1 Samuel Padgett 2016-10-24 17:40:19 UTC
This is not related to web console session length. I believe the hawkular-metrics container crashed, indicated by the 503 error codes. It looks to me like there are two hawkular-metrics replicas: one was healthy and one was not. It would explain why every other request fails in the screenshot.

I can not reproduce against the same server.

/cc Matt Wringe

Comment 15 Matt Wringe 2016-10-31 16:13:19 UTC
I am closing this issue as 'WORKSFORME' as we cannot reproduce it and we don't have the logs or other information available which would help us to debug this further. 

If you run into this issue again, please re-open this bug and gather the logs (the browser's console output, logs from Hawkular Metrics and Cassandra).


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