Bug 1641769 - Hawkular metrics pod is unstable
Summary: Hawkular metrics pod is unstable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.7.z
Assignee: Ruben Vargas Palma
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-22 17:02 UTC by Luke Stanton
Modified: 2023-03-24 14:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 23:36:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0617 0 None None None 2019-04-09 23:37:01 UTC

Description Luke Stanton 2018-10-22 17:02:13 UTC
Description of problem:

The hawkular-metrics pod has inconsistent behavior and generally isn't working well. The logs contain entries like the following:

2018-10-19 05:13:52,447 ERROR [stderr] (RxIoScheduler-3) Exception in thread "RxIoScheduler-3" java.lang.IllegalStateException: Exception thrown on Scheduler.Worker thread. Add `onError` handling.
...
2018-10-19 05:13:52,448 ERROR [stderr] (RxIoScheduler-3)        at java.lang.Thread.run(Thread.java:748)
2018-10-19 05:13:52,448 ERROR [stderr] (RxIoScheduler-3) Caused by: rx.exceptions.OnErrorNotImplementedException: unconfigured table data_temp_2018101914
...
2018-10-19 05:13:52,451 ERROR [stderr] (RxIoScheduler-3)        at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
...

How reproducible:
Consistently

Actual results:
Hawkular metrics pod is unstable

Expected results:
Metrics would work correctly

Comment 9 Junqi Zhao 2019-03-20 02:49:38 UTC
Did not find "unconfigured table **" error with
metrics-cassandra-v3.7.106-1
metrics-hawkular-metrics-v3.7.106-1
metrics-heapster-v3.7.106-1

Comment 11 errata-xmlrpc 2019-04-09 23:36:59 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, 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-2019:0617


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