Created attachment 1202409 [details] hawkular_metrics_log
Created attachment 1202410 [details] events
@ Matt, Hmm... The behavior is really weird, I've reproduced the issue on another env where all metrics pods are deployed on same node, so I give up the decision that this occur on seperate nodes. So far , the only thing I confirm is: this only occur with images on registry.ops.openshift.com
@mwringe @tdawson we hit a similar issue on AWS today when try to deploy metrics 3.3.0, could you help to build the images and sync to registry.ops.openshift.com/openshift3
@penli Yep, but it will most likely take a few days for it to be available.
@mwringe thanks.
I think you are running into HWKMETRICS-458. It is a schema installation/upgrade issue which can occur if hawkular-metrics is shutdown before the schema updates are finished being applied. When hawkular-metrics starts back up, it resumes schema updates but incorrectly tries to apply them to the system keyspace. The work around for now is to shutdown both Cassandra and hawkular-metrics, purge Cassandra's data and commit log directories, and then restart them. In order to avoid this error for now you will have to let hawkular-metrics fully initialize before shutting it down; otherwise, you will run into this again.
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-2016:2015