[
https://issues.jboss.org/browse/HAWKULARQE-32?page=com.atlassian.jira.plu...
]
Sunil kondkar commented on HAWKULARQE-32:
-----------------------------------------
Tested manually as below:
1) create/start cassandra version 3.10
ccm create hawkular -v 3.10 -n 1
ccm updateconf "start_rpc: true"
ccm start
2) Start hawkular service version 33
./standalone.sh -Dhawkular.rest.user=jdoe -Dhawkular.rest.password=password
-Dhawkular.agent.enabled=true
3) Stopped cassandra with 'ccm stop' when I see below in logs
08:03:14,852 INFO [org.hawkular.metrics.schema.SchemaService]
(metricsservice-lifecycle-thread) Creating table metrics_tags_idx
08:03:16,038 INFO [org.hawkular.metrics.schema.SchemaService]
(metricsservice-lifecycle-thread) Creating table metrics_idx
4) Stopped hawkular services
5) Started cassandra with ccm start
6) Verified hawkular service continues schema creation.
Cassandra/Hawkular Schema Test
------------------------------
Key: HAWKULARQE-32
URL:
https://issues.jboss.org/browse/HAWKULARQE-32
Project: Hawkular QE
Issue Type: Task
Reporter: Matt Mahoney
Assignee: Sunil kondkar
Test case request from Heiko (verbatim):
Start C*,wait until up. Start metrics/h-services
and once it starts schema creation (watch the logs), kill C*. Stop
h-services. Start C* again and then h-services,it should continue Schema
creation
While I was talking about h-services here, this applies foremost to
h-metrics (which is also used inside
of h-services).
Also I think Juca had a variation of this yesterday:
deploy h-metrics + C* into Openshift and then scale h-metrics up and
down at will.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)