本文介绍了Datastax opscenter升级无法显示统计信息的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我昨天将Opscenter从5.1.2升级到5.2.0,现在仪表板上的任何图表都没有显示任何统计信息.

I upgraded Opscenter from 5.1.2 to 5.2.0 yesterday, and now none of the graphs on the Dashboard are showing any statistics.

我的集群是具有以下版本的datastax企业版4.5.1:

My cluster is datastax enterprise 4.5.1 with the following versions:

cqlsh 4.1.1 | Cassandra 2.0.8.39 | CQL spec 3.1.1 | Thrift protocol 19.39.0

我正在将此集群用于solr的搜索工作量. agent.log充满以下内容:

I'm using this cluster for a search workload with solr. The agent.log is filled with the following:

INFO [qtp1313948736-24] 2015-08-06 12:30:52,211 New JMX connection (127.0.0.1:7199) INFO [qtp1313948736-24] 2015-08-06 12:30:52,214 New JMX connection (127.0.0.1:7199) INFO [qtp1313948736-24] 2015-08-06 12:30:52,218 HTTP: :get /cluster/solr-cores {} - 200 INFO [jmx-metrics-1] 2015-08-06 12:30:57,186 New JMX connection (127.0.0.1:7199) INFO [jmx-metrics-1] 2015-08-06 12:30:57,191 New JMX connection (127.0.0.1:7199)ERROR [cassandra-processor-4] 2015-08-06 12:31:15,082 Error when proccessing cassandra callcom.datastax.driver.core.exceptions.InvalidQueryException: Unknown identifier timestamp

INFO [qtp1313948736-24] 2015-08-06 12:30:52,211 New JMX connection (127.0.0.1:7199) INFO [qtp1313948736-24] 2015-08-06 12:30:52,214 New JMX connection (127.0.0.1:7199) INFO [qtp1313948736-24] 2015-08-06 12:30:52,218 HTTP: :get /cluster/solr-cores {} - 200 INFO [jmx-metrics-1] 2015-08-06 12:30:57,186 New JMX connection (127.0.0.1:7199) INFO [jmx-metrics-1] 2015-08-06 12:30:57,191 New JMX connection (127.0.0.1:7199)ERROR [cassandra-processor-4] 2015-08-06 12:31:15,082 Error when proccessing cassandra callcom.datastax.driver.core.exceptions.InvalidQueryException: Unknown identifier timestamp

有什么想法吗?

推荐答案

升级时迁移失败.可以使用describe keyspace "OpsCenter"浏览架构,找到未升级到5.2.0的表(请参见注释).所做的更改在这里:

The migration on upgrade failed. Can look through schema with describe keyspace "OpsCenter" and find tables not upgraded to 5.2.0 (look at comment). The changes made are here:

https://gist.github.com/philip-doctor/2b7c87f551a35a5c7c79

-- depending on how far through the migration you progressed, parts of this may fail
-- this assumes you're using the default name of "OpsCenter" for the opscenter keyspace, otherwise
-- you'll have to rename the "OpsCenter" part.

ALTER TABLE "OpsCenter"."events" ADD message text;
ALTER TABLE "OpsCenter"."events" ADD column_family text;
ALTER TABLE "OpsCenter"."events" ADD target_node text;
ALTER TABLE "OpsCenter"."events" ADD event_source text;
ALTER TABLE "OpsCenter"."events" ADD "keyspace" text;
ALTER TABLE "OpsCenter"."events" ADD api_source_ip text;
ALTER TABLE "OpsCenter"."events" ADD user text;
ALTER TABLE "OpsCenter"."events" ADD source_node text;
ALTER TABLE "OpsCenter"."events" with comment = '{"info": "OpsCenter management data.", "version": [5, 2, 0]}';

ALTER TABLE "OpsCenter"."rollups60" RENAME column1 to timestamp;
ALTER TABLE "OpsCenter"."rollups60" with comment = '{"info": "OpsCenter management data.", "version": [5, 2, 0]}';
ALTER TABLE "OpsCenter"."rollups300" RENAME column1 to timestamp;
ALTER TABLE "OpsCenter"."rollups300" with comment = '{"info": "OpsCenter management data.", "version": [5, 2, 0]}';
ALTER TABLE "OpsCenter"."rollups7200" RENAME column1 to timestamp;
ALTER TABLE "OpsCenter"."rollups7200" with comment = '{"info": "OpsCenter management data.", "version": [5, 2, 0]}';
ALTER TABLE "OpsCenter"."rollups86400" RENAME column1 to timestamp;
ALTER TABLE "OpsCenter"."rollups86400" with comment = '{"info": "OpsCenter management data.", "version": [5, 2, 0]}';

这篇关于Datastax opscenter升级无法显示统计信息的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-23 07:07